Changes between Version 2 and Version 3 of TracNotification
- Timestamp:
- 2014-01-26 00:59:46 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracNotification
v2 v3 18 18 19 19 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. 20 21 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 22 21 23 == Configuring SMTP Notification == … … 39 41 * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). 40 42 * '''`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. 43 * '''`ignore_domains`''': Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains). 41 44 * '''`mime_encoding`''': (''since 0.10'') This option allows selecting the MIME encoding scheme. Supported values: 42 45 * `none`: default value, uses 7bit encoding if the text is plain ASCII, or 8bit otherwise. … … 46 49 * '''`email_sender`''': (''since 0.12'') Name of the component implementing `IEmailSender`. This component is used by the notification system to send emails. Trac currently provides the following components: 47 50 * `SmtpEmailSender`: connects to an SMTP server (default). 48 * `SendmailEmailSender`: runs a `sendmail`-compatible executable. 51 * `SendmailEmailSender`: runs a `sendmail`-compatible executable. 49 52 50 53 Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. … … 95 98 === Customizing the e-mail content === 96 99 97 The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/t icket/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:100 The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/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: 98 101 99 102 {{{ 100 103 $ticket_body_hdr 101 104 $ticket_props 102 #choose ticket.new 103 #when True 105 {% choose ticket.new %}\ 106 {% when True %}\ 104 107 $ticket.description 105 #end 106 #otherwise 107 #if changes_body 108 Changes (by $change.author): 108 {% end %}\ 109 {% otherwise %}\ 110 {% if changes_body %}\ 111 ${_('Changes (by %(author)s):', author=change.author)} 109 112 110 113 $changes_body 111 #end 112 #if changes_descr 113 #if not changes_body and not change.comment and change.author 114 Description changed by $change.author: 115 #end 114 {% end %}\ 115 {% if changes_descr %}\ 116 {% if not changes_body and not change.comment and change.author %}\ 117 ${_('Description changed by %(author)s:', author=change.author)} 118 {% end %}\ 116 119 $changes_descr 117 120 -- 118 #end 119 #if change.comment 120 121 Comment${not changes_body and '(by %s)' % change.author or ''}: 121 {% end %}\ 122 {% if change.comment %}\ 123 124 ${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)} 122 125 123 126 $change.comment 124 #end 125 #end 126 #end 127 {% end %}\ 128 {% end %}\ 129 {% end %}\ 127 130 128 131 -- 129 Ticket URL: <$ticket.link> 132 ${_('Ticket URL: <%(link)s>', link=ticket.link)} 130 133 $project.name <${project.url or abs_href()}> 131 134 $project.descr … … 157 160 }}} 158 161 162 163 == Customizing e-mail content for MS Outlook == 164 165 Out-of-the-box, MS Outlook normally presents plain text e-mails with a variable-width font; 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]. 166 167 Replace the following second row in the template: 168 {{{ 169 $ticket_props 170 }}} 171 172 with this instead (''requires Python 2.6 or later''): 173 {{{ 174 -------------------------------------------------------------------------- 175 {% with 176 pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in 177 [c.strip() for c in 178 ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]]; 179 sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone', 180 'Component', 'Severity', 'Resolution', 'Keywords'] %}\ 181 ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)} 182 {% end %}\ 183 -------------------------------------------------------------------------- 184 }}} 185 186 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. 187 {{{#!div style="margin: 1em 1.75em; border:1px dotted" 188 {{{#!html 189 #42: testing<br /> 190 --------------------------------------------------------------------------<br /> 191 <table cellpadding=0> 192 <tr><td>Reporter:</td><td>jonas@example.com</td></tr> 193 <tr><td>Owner:</td><td>anonymous</td></tr> 194 <tr><td>Type:</td><td>defect</td></tr> 195 <tr><td>Status:</td><td>assigned</td></tr> 196 <tr><td>Priority:</td><td>lowest</td></tr> 197 <tr><td>Milestone:</td><td>0.9</td></tr> 198 <tr><td>Component:</td><td>report system</td></tr> 199 <tr><td>Severity:</td><td>major</td></tr> 200 <tr><td>Resolution:</td><td> </td></tr> 201 <tr><td>Keywords:</td><td> </td></tr> 202 </table> 203 --------------------------------------------------------------------------<br /> 204 Changes:<br /> 205 <br /> 206 * component: changset view => search system<br /> 207 * priority: low => highest<br /> 208 * owner: jonas => anonymous<br /> 209 * cc: daniel@example.com =><br /> 210 daniel@example.com, jonas@example.com<br /> 211 * status: new => assigned<br /> 212 <br /> 213 Comment:<br /> 214 I'm interested too!<br /> 215 <br /> 216 --<br /> 217 Ticket URL: <http://example.com/trac/ticket/42><br /> 218 My Project <http://myproj.example.com/><br /> 219 }}} 220 }}} 221 222 **Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which shall be part of the mail they have to be added to `sel`, example: 223 {{{ 224 sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2'] 225 }}} 226 227 However, it's not as perfect as an automatically HTML-formatted e-mail would be, but presented ticket properties are at least readable by default in MS Outlook... 228 229 159 230 == Using GMail as the SMTP relay host == 160 231