Changes between Version 2 and Version 3 of TracNotification
- Timestamp:
- Jun 8, 2011, 7:44:12 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracNotification
v2 v3 2 2 [[TracGuideToc]] 3 3 4 [[PageOutline]] 5 4 6 Trac supports notification about ticket changes via email. 5 7 … … 9 11 10 12 == Receiving Notification Mails == 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).13 When reporting a new ticket or adding a comment, enter a valid email address or your 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 14 13 15 This is useful to keep up-to-date on an issue or enhancement request that interests you. 14 16 17 === How to use your username to receive notification mails === 18 19 To receive notification mails, you can either enter a full email address or your username. To get notified with a simple username or login, you need to specify a valid email address in the ''Preferences'' page. 20 21 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. 22 15 23 == Configuring SMTP Notification == 24 25 '''Important:''' For TracNotification to work correctly, the `[trac] base_url` option must be set in [wiki:TracIni trac.ini]. 16 26 17 27 === Configuration Options === … … 70 80 * `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`. 71 81 82 === Customizing the e-mail content === 83 84 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: 85 86 {{{ 87 $ticket_body_hdr 88 $ticket_props 89 #choose ticket.new 90 #when True 91 $ticket.description 92 #end 93 #otherwise 94 #if changes_body 95 Changes (by $change.author): 96 97 $changes_body 98 #end 99 #if changes_descr 100 #if not changes_body and not change.comment and change.author 101 Description changed by $change.author: 102 #end 103 $changes_descr 104 -- 105 #end 106 #if change.comment 107 108 Comment${not changes_body and '(by %s)' % change.author or ''}: 109 110 $change.comment 111 #end 112 #end 113 #end 114 115 -- 116 Ticket URL: <$ticket.link> 117 $project.name <${project.url or abs_href()}> 118 $project.descr 119 }}} 72 120 == Sample Email == 73 121 {{{ … … 122 170 }}} 123 171 172 For Trac .10, use the filter: 173 {{{ 174 from:(<smtp_from>) (("Reporter: <username>" -Changes -Comment) OR "Changes (by <username>)" OR "Comment (by <username>)") 175 }}} 176 124 177 to delete these notifications. 125 178 … … 164 217 Relevant ML threads: 165 218 * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518 166 219 220 For SELinux in Fedora 10: 221 {{{ 222 $ setsebool -P httpd_can_sendmail 1 223 }}} 167 224 === ''Suspected spam'' error === 168 225 … … 172 229 173 230 Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, it is recommended to stick with the Base64 encoding. 231 232 === ''501, 5.5.4 Invalid Address'' error === 233 234 On IIS 6.0 you could get a 235 {{{ 236 Failure sending notification on change to ticket #1: SMTPHeloError: (501, '5.5.4 Invalid Address') 237 }}} 238 in the trac log. Have a look [http://support.microsoft.com/kb/291828 here] for instructions on resolving it. 239 174 240 175 241 ----