Changes between Initial Version and Version 1 of TracNotification

06/08/12 10:47:00 (11 years ago)



  • TracNotification

    v1 v1  
     1= Email Notification of Ticket Changes =
     4Trac supports notification of ticket changes via email.
     6Email notification is useful to keep users up-to-date on tickets/issues of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list. For example, this is how the [ Trac-tickets] mailing list is set up.
     8Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini].
     10== Receiving Notification Mails ==
     11When 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).
     13This is useful to keep up-to-date on an issue or enhancement request that interests you.
     15=== How to use your username to receive notification mails ===
     17To 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.
     19Alternatively, 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.
     21== Configuring SMTP Notification ==
     23'''Important:''' For TracNotification to work correctly, the `[trac] base_url` option must be set in [wiki:TracIni trac.ini].
     25=== Configuration Options ===
     26These are the available options for the `[notification]` section in trac.ini.
     28 * '''`smtp_enabled`''': Enable email notification.
     29 * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails.
     30 * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails.
     31 * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails.
     32 * '''`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.
     33 * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.''
     34 * '''`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
     35 * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default.
     36 * '''`always_notify_reporter`''':  Always send notifications to any address in the reporter field (default: false).
     37 * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false).
     38 * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true).
     39 * '''`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 * '''`use_short_addr`''': (''since 0.10'') Enable delivery of notifications to addresses that do not contain a domain (i.e. do not end with ''@<>'').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.
     41 * '''`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:
     42   * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines.
     43   * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64)
     44   * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered.
     45 * '''`ticket_subject_template`''': (''since 0.11'') A [ Genshi text template] snippet used to get the notification subject.
     46 * '''`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   * `SmtpEmailSender`: connects to an SMTP server (default).
     48   * `SendmailEmailSender`: runs a `sendmail`-compatible executable.
     50Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.
     52The following options are specific to email delivery through SMTP.
     53 * '''`smtp_server`''': SMTP server used for notification messages.
     54 * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server.
     55 * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account.
     56 * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account.
     57 * '''`use_tls`''': (''since 0.10'') Toggle to send notifications via a SMTP server using [ TLS], such as GMail.
     59The following option is specific to email delivery through a `sendmail`-compatible executable.
     60 * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options.
     62=== Example Configuration (SMTP) ===
     65smtp_enabled = true
     66smtp_server =
     67smtp_from =
     68smtp_replyto =
     69smtp_always_cc =,
     72=== Example Configuration (`sendmail`) ===
     75smtp_enabled = true
     76email_sender = SendmailEmailSender
     77sendmail_path = /usr/sbin/sendmail
     78smtp_from =
     79smtp_replyto =
     80smtp_always_cc =,
     83=== Customizing the e-mail subject ===
     84The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [ Genshi text template] snippet. The default value is:
     86$prefix #$ $summary
     88The following variables are available in the template:
     90 * `env`: The project environment (see [trac:source:/trunk/trac/]).
     91 * `prefix`: The prefix defined in `smtp_subject_prefix`.
     92 * `summary`: The ticket summary, with the old value if the summary was edited.
     93 * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/]). Individual ticket fields can be addressed by appending the field name separated by a dot, e.g. `$ticket.milestone`.
     95=== Customizing the e-mail content ===
     97The 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:
     103  #when True
     105  #end
     106  #otherwise
     107    #if changes_body
     108Changes (by $
     111    #end
     112    #if changes_descr
     113      #if not changes_body and not change.comment and
     114Description changed by $
     115      #end
     118    #end
     119    #if change.comment
     121Comment${not changes_body and '(by %s)' % or ''}:
     124    #end
     125  #end
     129Ticket URL: <$>
     130$ <${project.url or abs_href()}>
     133== Sample Email ==
     135#42: testing
     137       Id:  42             |      Status:  assigned               
     138Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
     139 Severity:  major          |   Milestone:  0.9                     
     140 Priority:  lowest         |     Version:  0.6                     
     141    Owner:  anonymous      |    Reporter:               
     144  * component:  changset view => search system
     145  * priority:  low => highest
     146  * owner:  jonas => anonymous
     147  * cc: =>
     149  * status:  new => assigned
     152I'm interested too!
     155Ticket URL: <>
     156My Project <>
     159== Using GMail as the SMTP relay host ==
     161Use the following configuration snippet
     164smtp_enabled = true
     165use_tls = true
     166mime_encoding = base64
     167smtp_server =
     168smtp_port = 587
     169smtp_user = user
     170smtp_password = password
     173where ''user'' and ''password'' match an existing GMail account, ''i.e.'' the ones you use to log in on []
     175Alternatively, you can use `smtp_port = 25`.[[br]]
     176You should not use `smtp_port = 465`. It will not work and your ticket submission may deadlock. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [comment:ticket:7107:2 #7107] for details.
     178== Filtering notifications for one's own changes ==
     179In Gmail, use the filter:
     182from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)")
     185For Trac .10, use the filter:
     187from:(<smtp_from>) (("Reporter: <username>" -Changes -Comment) OR "Changes (by <username>)" OR "Comment (by <username>)")
     190to delete these notifications.
     192In Thunderbird, there is no such solution if you use IMAP
     195The best you can do is to set "always_notify_updater" in conf/trac.ini to false.
     196You will however still get an email if you comment a ticket that you own or have reported.
     198You can also add this plugin:
     201== Troubleshooting ==
     203If you cannot get the notification working, first make sure the log is activated and have a look at the log to find if an error message has been logged. See TracLogging for help about the log feature.
     205Notification errors are not reported through the web interface, so the user who submit a change or a new ticket never gets notified about a notification failure. The Trac administrator needs to look at the log to find the error trace.
     207=== ''Permission denied'' error ===
     209Typical error message:
     211  ...
     212  File ".../", line 303, in connect
     213    raise socket.error, msg
     214  error: (13, 'Permission denied')
     217This error usually comes from a security settings on the server: many Linux distributions do not let the web server (Apache, ...) to post email message to the local SMTP server.
     219Many users get confused when their manual attempts to contact the SMTP server succeed:
     221telnet localhost 25
     223The trouble is that a regular user may connect to the SMTP server, but the web server cannot:
     225sudo -u www-data telnet localhost 25
     228In such a case, you need to configure your server so that the web server is authorized to post to the SMTP server. The actual settings depend on your Linux distribution and current security policy. You may find help browsing the Trac [trac:MailingList MailingList] archive.
     230Relevant ML threads:
     231 * SELinux:
     233For SELinux in Fedora 10:
     235$ setsebool -P httpd_can_sendmail 1
     237=== ''Suspected spam'' error ===
     239Some SMTP servers may reject the notification email sent by Trac.
     241The default Trac configuration uses Base64 encoding to send emails to the recipients. The whole body of the email is encoded, which sometimes trigger ''false positive'' SPAM detection on sensitive email servers. In such an event, it is recommended to change the default encoding to "quoted-printable" using the `mime_encoding` option.
     243Quoted 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.
     245=== ''501, 5.5.4 Invalid Address'' error ===
     247On IIS 6.0 you could get a
     249Failure sending notification on change to ticket #1: SMTPHeloError: (501, '5.5.4 Invalid Address')
     251in the trac log. Have a look [ here] for instructions on resolving it.
     255See also: TracTickets, TracIni, TracGuide