| 11 | | When reporting a new ticket or adding a comment, enter a valid email address in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket (depending on how notification is configured). |
| 12 | | |
| 13 | | This is useful to keep up-to-date on an issue or enhancement request that interests you. |
| | 11 | When reporting a new ticket or adding a comment, enter a valid email address or your Trac username in the ''reporter'', ''assigned to/owner'' or ''cc'' field. Trac will automatically send you an email when changes are made to the ticket, depending on how notification is configured. |
| | 12 | |
| | 13 | === How to use your username to receive notification mails === |
| | 14 | |
| | 15 | To receive notification mails, you can either enter a full email address or your Trac username. To get notified with a simple username or login, you need to specify a valid email address in the ''Preferences'' page. |
| | 16 | |
| | 17 | Alternatively, a default domain name ('''`smtp_default_domain`''') can be set in the TracIni file, see [#ConfigurationOptions Configuration Options] below. In this case, the default domain will be appended to the username, which can be useful for an "Intranet" kind of installation. |
| | 18 | |
| | 19 | When using apache and mod_kerb for authentication against Kerberos / Active Directory, usernames take the form ('''`username@EXAMPLE.LOCAL`'''). To avoid this being interpreted as an email address, add the Kerberos domain to ('''`ignore_domains`'''). |
| | 20 | |
| | 21 | === Ticket attachment notifications |
| | 22 | |
| | 23 | Since 1.0.3 Trac will send notifications when a ticket attachment is added or deleted. Usually attachment notifications will be enabled in an environment by default. To disable the attachment notifications for an environment the `TicketAttachmentNotifier` component must be disabled: |
| | 24 | {{{#!ini |
| | 25 | [components] |
| | 26 | trac.ticket.notification.TicketAttachmentNotifier = disabled |
| | 27 | }}} |
| 18 | | These are the available options for the `[notification]` section in trac.ini. |
| 19 | | |
| 20 | | * '''`smtp_enabled`''': Enable email notification. |
| 21 | | * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails. |
| 22 | | * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails. |
| 23 | | * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails. |
| 24 | | * '''`smtp_default_domain`''': (''since 0.10'') Append the specified domain to addresses that do not contain one. Fully qualified addresses are not modified. The default domain is appended to all username/login for which an email address cannot be found from the user settings. |
| 25 | | * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.'' |
| 26 | | * '''`smtp_always_bcc`''': (''since 0.10'') List of email addresses to always send notifications to, but keeps addresses not visible from other recipients of the notification email |
| 27 | | * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default. |
| 28 | | * '''`always_notify_reporter`''': Always send notifications to any address in the reporter field (default: false). |
| 29 | | * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false). |
| 30 | | * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true). |
| 31 | | * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). |
| 32 | | * '''`use_short_addr`''': (''since 0.10'') Enable delivery of notifications to addresses that do not contain a domain (i.e. do not end with ''@<domain.com>'').This option is useful for intranets, where the SMTP server can handle local addresses and map the username/login to a local mailbox. See also `smtp_default_domain`. Do not use this option with a public SMTP server. |
| 33 | | * '''`mime_encoding`''': (''since 0.10'') E-mail notifications are always sent in 7-bit mode. This option allows to select the MIME encoding scheme. Supported values: |
| 34 | | * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| 35 | | * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) |
| 36 | | * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. |
| 37 | | * '''`ticket_subject_template`''': (''since 0.11'') A [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet used to get the notification subject. |
| 38 | | |
| 39 | | Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. |
| 40 | | |
| 41 | | The following options are specific to email delivery through SMTP. |
| 42 | | * '''`smtp_server`''': SMTP server used for notification messages. |
| 43 | | * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server. |
| 44 | | * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account. |
| 45 | | * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account. |
| 46 | | * '''`use_tls`''': (''since 0.10'') Toggle to send notifications via a SMTP server using [http://en.wikipedia.org/wiki/Transport_Layer_Security TLS], such as GMail. |
| 47 | | |
| | 34 | These are the available options for the `[notification]` section in trac.ini: |
| | 35 | |
| | 36 | [[TracIni(notification)]] |
| 70 | | * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, e.g. `$ticket.milestone`. |
| | 69 | * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, eg `$ticket.milestone`. |
| | 70 | |
| | 71 | === Customizing the e-mail content === |
| | 72 | |
| | 73 | The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/ticket/templates`. You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this: |
| | 74 | |
| | 75 | {{{ |
| | 76 | $ticket_body_hdr |
| | 77 | $ticket_props |
| | 78 | {% choose ticket.new %}\ |
| | 79 | {% when True %}\ |
| | 80 | $ticket.description |
| | 81 | {% end %}\ |
| | 82 | {% otherwise %}\ |
| | 83 | {% if changes_body %}\ |
| | 84 | ${_('Changes (by %(author)s):', author=change.author)} |
| | 85 | |
| | 86 | $changes_body |
| | 87 | {% end %}\ |
| | 88 | {% if changes_descr %}\ |
| | 89 | {% if not changes_body and not change.comment and change.author %}\ |
| | 90 | ${_('Description changed by %(author)s:', author=change.author)} |
| | 91 | {% end %}\ |
| | 92 | $changes_descr |
| | 93 | -- |
| | 94 | {% end %}\ |
| | 95 | {% if change.comment %}\ |
| | 96 | |
| | 97 | ${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)} |
| | 98 | |
| | 99 | $change.comment |
| | 100 | {% end %}\ |
| | 101 | {% end %}\ |
| | 102 | {% end %}\ |
| | 103 | |
| | 104 | -- |
| | 105 | ${_('Ticket URL: <%(link)s>', link=ticket.link)} |
| | 106 | $project.name <${project.url or abs_href()}> |
| | 107 | $project.descr |
| | 108 | }}} |
| | 136 | == Customizing e-mail content for MS Outlook == |
| | 137 | |
| | 138 | MS Outlook normally presents plain text e-mails with a variable-width font, and as a result the ticket properties table will most certainly look like a mess in MS Outlook. This can be fixed with some customization of the [#Customizingthee-mailcontent e-mail template]. |
| | 139 | |
| | 140 | Replace the following second row in the template: |
| | 141 | {{{ |
| | 142 | $ticket_props |
| | 143 | }}} |
| | 144 | |
| | 145 | with this (requires Python 2.6 or later): |
| | 146 | {{{ |
| | 147 | -------------------------------------------------------------------------- |
| | 148 | {% with |
| | 149 | pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in |
| | 150 | [c.strip() for c in |
| | 151 | ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]]; |
| | 152 | sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone', |
| | 153 | 'Component', 'Severity', 'Resolution', 'Keywords'] %}\ |
| | 154 | ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)} |
| | 155 | {% end %}\ |
| | 156 | -------------------------------------------------------------------------- |
| | 157 | }}} |
| | 158 | |
| | 159 | The table of ticket properties is replaced with a list of a selection of the properties. A tab character separates the name and value in such a way that most people should find this more pleasing than the default table when using MS Outlook. |
| | 160 | {{{#!div style="margin: 1em 1.75em; border:1px dotted" |
| | 161 | {{{#!html |
| | 162 | #42: testing<br /> |
| | 163 | --------------------------------------------------------------------------<br /> |
| | 164 | <table cellpadding=0> |
| | 165 | <tr><td>Reporter:</td><td>jonas@example.com</td></tr> |
| | 166 | <tr><td>Owner:</td><td>anonymous</td></tr> |
| | 167 | <tr><td>Type:</td><td>defect</td></tr> |
| | 168 | <tr><td>Status:</td><td>assigned</td></tr> |
| | 169 | <tr><td>Priority:</td><td>lowest</td></tr> |
| | 170 | <tr><td>Milestone:</td><td>0.9</td></tr> |
| | 171 | <tr><td>Component:</td><td>report system</td></tr> |
| | 172 | <tr><td>Severity:</td><td>major</td></tr> |
| | 173 | <tr><td>Resolution:</td><td> </td></tr> |
| | 174 | <tr><td>Keywords:</td><td> </td></tr> |
| | 175 | </table> |
| | 176 | --------------------------------------------------------------------------<br /> |
| | 177 | Changes:<br /> |
| | 178 | <br /> |
| | 179 | * component: changeset view => search system<br /> |
| | 180 | * priority: low => highest<br /> |
| | 181 | * owner: jonas => anonymous<br /> |
| | 182 | * cc: daniel@example.com =><br /> |
| | 183 | daniel@example.com, jonas@example.com<br /> |
| | 184 | * status: new => assigned<br /> |
| | 185 | <br /> |
| | 186 | Comment:<br /> |
| | 187 | I'm interested too!<br /> |
| | 188 | <br /> |
| | 189 | --<br /> |
| | 190 | Ticket URL: <http://example.com/trac/ticket/42><br /> |
| | 191 | My Project <http://myproj.example.com/><br /> |
| | 192 | }}} |
| | 193 | }}} |
| | 194 | |
| | 195 | **Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which are to be part of the mail, then they have to be added to `sel`. Example: |
| | 196 | {{{ |
| | 197 | sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2'] |
| | 198 | }}} |
| | 199 | |
| | 200 | However, the solution is still a workaround to an automatically HTML-formatted e-mail. |
| | 201 | |
