| 4 | | Trac supports notification about ticket changes via email. |
| 5 | | |
| 6 | | 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 [http://lists.edgewall.com/archive/trac-tickets/ Trac-tickets] mailing list is set up. |
| 7 | | |
| 8 | | Disabled by default, notification can be activated and configured in [wiki:TracIni trac.ini]. |
| 9 | | |
| 10 | | == 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). |
| 12 | | |
| 13 | | This is useful to keep up-to-date on an issue or enhancement request that interests you. |
| 14 | | |
| 15 | | == Configuring SMTP Notification == |
| 16 | | |
| 17 | | === Configuration Options === |
| 18 | | These are the available options for the ''[notification]'' section in trac.ini. |
| 19 | | * '''smtp_enabled''': Enable email notification. |
| 20 | | * '''smtp_server''': SMTP server used for notification messages. |
| 21 | | * '''smtp_user''': (''since 0.9'') User name for authentication SMTP account. |
| 22 | | * '''smtp_password''': (''since 0.9'') Password for authentication SMTP account. |
| 23 | | * '''smtp_from''': Email address to use for ''Sender''-headers in notification emails. |
| 24 | | * '''smtp_replyto''': Email address to use for ''Reply-To''-headers in notification emails. |
| 25 | | * '''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. |
| 26 | | * '''smtp_always_cc''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.'' |
| 27 | | * '''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 |
| 28 | | * '''always_notify_reporter''': Always send notifications to any address in the reporter field. |
| 29 | | * '''always_notify_owner''': (''since 0.9'') Always send notifications to the address in the owner field. |
| 30 | | * '''always_notify_updater''': (''since 0.10'') Always send a notification to the updater of a ticket. |
| 31 | | * '''use_public_cc''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). |
| 32 | | * '''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. |
| 33 | | * '''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: |
| 34 | | * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| 35 | | * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) |
| 36 | | * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. |
| 37 | | |
| 38 | | Either '''smtp_from''' or '''smtp_replyto''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. |
| 39 | | |
| 40 | | === Example Configuration === |
| 41 | | |
| 42 | | {{{ |
| | 4 | Trac supports notification of ticket changes via email. |
| | 5 | |
| | 6 | Email 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. |
| | 7 | |
| | 8 | Disabled by default, notification can be activated and configured in [TracIni trac.ini]. |
| | 9 | |
| | 10 | == Receiving Notification Mails |
| | 11 | When 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. |
| | 12 | |
| | 13 | === How to use your username to receive notification mails |
| | 14 | |
| | 15 | To 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]. |
| | 16 | |
| | 17 | 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. |
| | 18 | |
| | 19 | 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 | |
| | 21 | === Ticket attachment notifications |
| | 22 | |
| | 23 | Since 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: |
| | 24 | {{{#!ini |
| | 25 | [components] |
| | 26 | trac.ticket.notification.TicketAttachmentNotifier = disabled |
| | 27 | }}} |
| | 28 | |
| | 29 | == Configuring SMTP Notification |
| | 30 | |
| | 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. |
| | 32 | |
| | 33 | === Configuration Options |
| | 34 | These are the available options for the `[notification]` section in trac.ini: |
| | 35 | |
| | 36 | [[TracIni(section=notification)]] |
| | 37 | |
| | 38 | === Example Configuration (SMTP) |
| | 39 | {{{#!ini |
| 51 | | == Sample Email == |
| | 48 | === Example Configuration (`sendmail`) |
| | 49 | {{{#!ini |
| | 50 | [notification] |
| | 51 | smtp_enabled = true |
| | 52 | email_sender = SendmailEmailSender |
| | 53 | sendmail_path = /usr/sbin/sendmail |
| | 54 | smtp_from = notifier@example.com |
| | 55 | smtp_replyto = myproj@projects.example.com |
| | 56 | smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com |
| | 57 | }}} |
| | 58 | |
| | 59 | === Subscriber Configuration |
| | 60 | The default subscriptions are configured in the [TracIni#notification-subscriber-section "[notification-subscriber]"] section. |
| | 61 | |
| | 62 | [[TracIni(section=notification-subscriber)]] |
| | 63 | |
| | 64 | Each user can override these defaults in their ''Notifications'' preferences. |
| | 65 | |
| | 66 | For 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. |
| | 67 | |
| | 68 | The 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. |
| | 69 | |
| | 70 | The 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. |
| | 80 | |
| | 81 | === Example Configuration (default subscriptions) |
| | 82 | {{{#!ini |
| | 83 | [notification-subscriber] |
| | 84 | always_notify_owner = TicketOwnerSubscriber |
| | 85 | always_notify_owner.distributor = email |
| | 86 | always_notify_owner.priority = 100 |
| | 87 | always_notify_owner.adverb = always |
| | 88 | always_notify_owner.format = text/plain |
| | 89 | |
| | 90 | always_notify_previous_updater = TicketPreviousUpdatersSubscriber |
| | 91 | |
| | 92 | never_notify_updater = TicketUpdaterSubscriber |
| | 93 | never_notify_updater.adverb = never |
| | 94 | never_notify_updater.priority = 0 |
| | 95 | |
| | 96 | notify_cc_html = CarbonCopySubscriber |
| | 97 | notify_cc_html.format = text/html |
| | 98 | }}} |
| | 99 | |
| | 100 | === Customizing the e-mail subject |
| | 101 | The e-mail subject can be customized with the `ticket_subject_template` option, which contains a [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet. The default value is: |
| | 102 | {{{#!genshi |
| | 103 | ${prefix} #${ticket.id}: ${summary} |
| | 104 | }}} |
| | 105 | The following variables are available in the template: |
| | 106 | |
| | 107 | * `env`: The project environment object (see [trac:source:branches/1.2-stable/trac/env.py env.py]). |
| | 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/model.py model.py]). Individual ticket fields can be accessed by appending the field name separated by a dot, eg `${ticket.milestone}`. |
| | 111 | |
| | 112 | === Customizing the e-mail content |
| | 113 | |
| | 114 | 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 is: |
| | 115 | |
| | 116 | {{{#!genshi |
| | 117 | $ticket_body_hdr |
| | 118 | $ticket_props |
| | 119 | {% choose ticket.new %}\ |
| | 120 | {% when True %}\ |
| | 121 | $ticket.description |
| | 122 | {% end %}\ |
| | 123 | {% otherwise %}\ |
| | 124 | {% if changes_body %}\ |
| | 125 | ${_('Changes (by %(author)s):', author=change.author)} |
| | 126 | |
| | 127 | $changes_body |
| | 128 | {% end %}\ |
| | 129 | {% if changes_descr %}\ |
| | 130 | {% if not changes_body and not change.comment and change.author %}\ |
| | 131 | ${_('Description changed by %(author)s:', author=change.author)} |
| | 132 | {% end %}\ |
| | 133 | $changes_descr |
| | 134 | -- |
| | 135 | {% end %}\ |
| | 136 | {% if change.comment %}\ |
| | 137 | |
| | 138 | ${_('Comment:') if changes_body else _('Comment (by %(author)s):', author=change.author)} |
| | 139 | |
| | 140 | $change.comment |
| | 141 | {% end %}\ |
| | 142 | {% end %}\ |
| | 143 | {% end %}\ |
| | 144 | |
| | 145 | ${'-- '} |
| | 146 | ${_('Ticket URL: <%(link)s>', link=ticket.link)} |
| | 147 | $project.name <${project.url or abs_href()}> |
| | 148 | $project.descr |
| | 149 | }}} |
| | 150 | |
| | 151 | See the [trac:CookBook/Notification/Templates cookbook] for additional template customization recipes. |
| | 152 | |
| | 153 | == Sample Email |
| 77 | | == Troubleshooting == |
| 78 | | |
| 79 | | 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. |
| 80 | | |
| 81 | | 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. |
| 82 | | |
| 83 | | === ''Permission denied'' error === |
| | 179 | == Using GMail as the SMTP relay host |
| | 180 | |
| | 181 | Use the following configuration snippet: |
| | 182 | {{{#!ini |
| | 183 | [notification] |
| | 184 | smtp_enabled = true |
| | 185 | use_tls = true |
| | 186 | mime_encoding = base64 |
| | 187 | smtp_server = smtp.gmail.com |
| | 188 | smtp_port = 587 |
| | 189 | smtp_user = user |
| | 190 | smtp_password = password |
| | 191 | }}} |
| | 192 | |
| | 193 | where ''user'' and ''password'' match an existing GMail account, ie the ones you use to log in on [http://gmail.com]. |
| | 194 | |
| | 195 | Alternatively, you can use `smtp_port = 25`.[[br]] |
| | 196 | You 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. |
| | 197 | |
| | 198 | == Troubleshooting |
| | 199 | |
| | 200 | If notifications are not working, inspect the [TracLogging log] for error messages. |
| | 201 | |
| | 202 | Notification 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. |
| | 203 | |
| | 204 | === ''Permission denied'' error |
