Email Notification of Ticket Changes

[TracGuideToc]

Trac supports notification about ticket changes via email.

Email 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.

Disabled by default, notification can be activated and configured in trac.ini.

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).

This is useful to keep up-to-date on an issue or enhancement request that interests you.

These are the available options for the notification section in trac.ini.

• smtp_enabled: Enable email notification.
• smtp_server: SMTP server used for notification messages.
• smtp_user: (since 0.9) User name for authentication SMTP account.
• smtp_password: (since 0.9) Password for authentication SMTP account.
• smtp_from: Email address to use for Sender-headers in notification emails.
• smtp_replyto: Email address to use for Reply-To-headers in notification emails.
• 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.
• smtp_always_cc: List of email addresses to always send notifications to. Typically used to post ticket changes to a dedicated mailing list.
• 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
• always_notify_reporter: Always send notifications to any address in the reporter field.
• always_notify_owner: (since 0.9) Always send notifications to the address in the owner field.
• always_notify_updater: (since 0.10) Always send a notification to the updater of a ticket.
• use_public_cc: (since 0.10) Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is Bcc: - hidden copy).
• 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.
• 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:
  • `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines.
  • `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64)
  • `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered.

Either smtp_from or smtp_replyto (or both) must be set, otherwise Trac refuses to send notification mails.

[[:notification]]
smtp_enabled = true
smtp_server = mail.example.com
smtp_from = notifier@example.com
smtp_replyto = myproj@projects.example.com
smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com

#42: testing
---------------------------+------------------------------------------------
       Id:  42             |      Status:  assigned                
Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
 Severity:  major          |   Milestone:  0.9                     
 Priority:  lowest         |     Version:  0.6                     
    Owner:  anonymous      |    Reporter:  jonas@example.com               
---------------------------+------------------------------------------------
Changes:
   * component:  changset view => search system
   * priority:  low => highest
   * owner:  jonas => anonymous
   * cc:  daniel@example.com =>
         daniel@example.com, jonas@example.com
   * status:  new => assigned

Comment:
I'm interested too!

--
Ticket URL: <http://example.com/trac/ticket/42>
My Project <http://myproj.example.com/>

If 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.

Notification 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.

Typical error message:

  ...
  File ".../smtplib.py", line 303, in connect
    raise socket.error, msg
  error: (13, 'Permission denied')

This 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.

Many users get confused when their manual attempts to contact the SMTP server succeed:

telnet localhost 25

The trouble is that a regular user may connect to the SMTP server, but the web server cannot:

sudo -u www-data telnet localhost 25

In such a case, you need to configure your server so that the web server is authorize 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 MailingList archive.

Relevant ML threads:

• SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518

Some SMTP servers may reject the notification email sent by Trac.

The 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.

Quoted printable enconding works better with languages that use one of the Latin charsets. For Asian charsets, it is recommended to stick with the Base64 encoding.

See also: TracTickets, TracIni, TracGuide