Changes between Initial Version and Version 1 of TracNotification

Feb 16, 2019, 10:35:19 PM (3 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 of interest, and also provides a convenient way to post all ticket changes to a dedicated mailing list.
     8Disabled by default, notification can be activated and configured in [TracIni trac.ini].
     10== Receiving Notification Mails
     11When 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.
     13=== How to use your username to receive notification mails
     15To 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 your [/prefs preferences].
     17Alternatively, 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.
     19When 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`''').
     21=== Ticket attachment notifications
     23Since 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:
     26trac.ticket.notification.TicketAttachmentNotifier = disabled
     29== Configuring SMTP Notification
     31'''Important:''' The [[TracIni#trac-base_url-option|[trac] base_url]] option must be configured for links in the notification message to be correctly generated.
     33=== Configuration Options
     34These are the available options for the `[notification]` section in trac.ini:
     38=== Example Configuration (SMTP)
     41smtp_enabled = true
     42smtp_server =
     43smtp_from =
     44smtp_replyto =
     45smtp_always_cc =,
     48=== Example Configuration (`sendmail`)
     51smtp_enabled = true
     52email_sender = SendmailEmailSender
     53sendmail_path = /usr/sbin/sendmail
     54smtp_from =
     55smtp_replyto =
     56smtp_always_cc =,
     59=== Subscriber Configuration
     60The default subscriptions are configured in the [TracIni#notification-subscriber-section "[notification-subscriber]"] section.
     64Each user can override these defaults in their ''Notifications'' preferences.
     66For example to unsubscribe from notifications for one's own changes and comments, the rule "Never notify: I update a ticket" should be added above other subscription rules.
     68The subscription rule name on the left side of the `=` can be anything, it has no meaning outside this configuration file. The subscriber name on the right side of the `=` must be one of the subscribers listed in the above table.
     70The following attributes of default subscriptions can be configured:
     71* `.distributor` (Default: `email`)
     72  * Other values require plugins. For example `on-site` requires th:OnSiteNotificationsPlugin.
     73* `.priority` (Default: `100`)
     74  * Smaller values override larger values.
     75  * If you use `0`, then users will not be able to override this rule.
     76* `.adverb` (Default: `always`)
     77  * `never` can be used to silence other subscription rules with higher values.
     78* `.format` (Default: `text/plain`)
     79  * Other values require plugins. For example `text/html` requires th:TracHtmlNotificationPlugin.
     81=== Example Configuration (default subscriptions)
     84always_notify_owner = TicketOwnerSubscriber
     85always_notify_owner.distributor = email
     86always_notify_owner.priority = 100
     87always_notify_owner.adverb = always
     88always_notify_owner.format = text/plain
     90always_notify_previous_updater = TicketPreviousUpdatersSubscriber
     92never_notify_updater = TicketUpdaterSubscriber
     93never_notify_updater.adverb = never
     94never_notify_updater.priority = 0
     96notify_cc_html = CarbonCopySubscriber
     97notify_cc_html.format = text/html
     100=== Customizing the e-mail subject
     101The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [ Genshi text template] snippet. The default value is:
     103${prefix} #${}: ${summary}
     105The following variables are available in the template:
     107 * `env`: The project environment object (see [trac:source:branches/1.2-stable/trac/]).
     108 * `prefix`: The prefix defined in `smtp_subject_prefix`.
     109 * `summary`: The ticket summary, with the old value if the summary was edited.
     110 * `ticket`: The ticket model object (see [trac:source:branches/1.2-stable/trac/ticket/]). Individual ticket fields can be accessed by appending the field name separated by a dot, eg `${ticket.milestone}`.
     112=== Customizing the e-mail content
     114The 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 is:
     119{% choose %}\
     120{%   when True %}\
     122{%   end %}\
     123{%   otherwise %}\
     124{%     if changes_body %}\
     125${_('Changes (by %(author)s):',}
     128{%     end %}\
     129{%     if changes_descr %}\
     130{%       if not changes_body and not change.comment and %}\
     131${_('Description changed by %(author)s:',}
     132{%       end %}\
     135{%     end %}\
     136{%     if change.comment %}\
     138${_('Comment:') if changes_body else _('Comment (by %(author)s):',}
     141{%     end %}\
     142{%   end %}\
     143{% end %}\
     145${'-- '}
     146${_('Ticket URL: <%(link)s>',}
     147$ <${project.url or abs_href()}>
     151See the [trac:CookBook/Notification/Templates cookbook] for additional template customization recipes.
     153== Sample Email
     155#42: testing
     157       Id:  42             |      Status:  assigned               
     158Component:  report system  |    Modified:  Fri Apr  9 00:04:31 2004
     159 Severity:  major          |   Milestone:  0.9                     
     160 Priority:  lowest         |     Version:  0.6                     
     161    Owner:  anonymous      |    Reporter:               
     164  * component:  changeset view => search system
     165  * priority:  low => highest
     166  * owner:  jonas => anonymous
     167  * cc: =>
     169  * status:  new => assigned
     172I'm interested too!
     175Ticket URL: <>
     176My Project <>
     179== Using GMail as the SMTP relay host
     181Use the following configuration snippet:
     184smtp_enabled = true
     185use_tls = true
     186mime_encoding = base64
     187smtp_server =
     188smtp_port = 587
     189smtp_user = user
     190smtp_password = password
     193where ''user'' and ''password'' match an existing GMail account, ie the ones you use to log in on [].
     195Alternatively, you can use `smtp_port = 25`.[[br]]
     196You should not use `smtp_port = 465`. Doing so may deadlock your ticket submission. Port 465 is reserved for the SMTPS protocol, which is not supported by Trac. See [trac:comment:2:ticket:7107 #7107] for details.
     198== Troubleshooting
     200If notifications are not working, inspect the [TracLogging log] for error messages.
     202Notification errors are not always reported through the web interface, so the user who submits a change or creates a ticket may not get notified about a notification failure. The Trac administrator needs to look at the log to find the error message and traceback.
     204=== ''Permission denied'' error
     206Typical error message:
     208  ...
     209  File ".../", line 303, in connect
     210    raise socket.error, msg
     211  error: (13, 'Permission denied')
     214This error usually comes from a security settings on the server: many Linux distributions do not allow the web server (Apache, ...) to post email messages to the local SMTP server.
     216Many users get confused when their manual attempts to contact the SMTP server succeed:
     218telnet localhost 25
     220This is because a regular user may connect to the SMTP server, but the web server cannot:
     222sudo -u www-data telnet localhost 25
     225In 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 in the Trac [trac:MailingList MailingList] archive.
     227Relevant ML threads:
     228 * SELinux:
     230For SELinux in Fedora 10:
     232$ setsebool -P httpd_can_sendmail 1
     235=== ''Suspected spam'' error
     237Some SMTP servers may reject the notification email sent by Trac.
     239The 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, change the default encoding to "quoted-printable" using the `mime_encoding` option.
     241Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, stick with the Base64 encoding.
     244See also: TracTickets, TracIni, TracGuide, [trac:TracDev/NotificationApi]