| 10 | | == Receiving Notification Mails == |
| 11 | | 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 | | |
| 13 | | This is useful to keep up-to-date on an issue or enhancement request that interests you. |
| 14 | | |
| 15 | | === How to use your username to receive notification mails === |
| 16 | | |
| 17 | | 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. |
| 18 | | |
| 19 | | 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. |
| | 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 may send you an email when changes are made to the ticket, depending on how your notification preferences are configured. |
| | 12 | |
| | 13 | Permission groups can also be entered in the CC field, |
| | 14 | to notify all members of the group. |
| | 15 | |
| | 16 | === How to use your username to receive notification mails |
| | 17 | |
| | 18 | 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 the ''Preferences'' page. |
| | 19 | |
| | 20 | 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. |
| 27 | | === Configuration Options === |
| 28 | | These are the available options for the `[notification]` section in trac.ini. |
| 29 | | |
| 30 | | * '''`smtp_enabled`''': Enable email notification. |
| 31 | | * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails. |
| 32 | | * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails. |
| 33 | | * '''`smtp_from_author`''': (''since 1.0'') Use the author of a change (the reporter of a new ticket, or the author of a comment) as the `From:` header value in notification e-mails (default: false). If the author hasn't set an e-mail address, `smtp_from` and `smtp_from_name` are used instead. |
| 34 | | * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails. |
| 35 | | * '''`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. |
| 36 | | * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.'' |
| 37 | | * '''`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 |
| 38 | | * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default. |
| 39 | | * '''`always_notify_reporter`''': Always send notifications to any address in the reporter field (default: false). |
| 40 | | * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false). |
| 41 | | * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true). |
| 42 | | * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). |
| 43 | | * '''`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. |
| 44 | | * '''`ignore_domains`''': Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains). |
| 45 | | * '''`mime_encoding`''': (''since 0.10'') This option allows selecting the MIME encoding scheme. Supported values: |
| 46 | | * `none`: default value, uses 7bit encoding if the text is plain ASCII, or 8bit otherwise. |
| 47 | | * `base64`: works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| 48 | | * `qp` or `quoted-printable`: best for european languages (more compact than base64) if 8bit encoding cannot be used. |
| 49 | | * '''`ticket_subject_template`''': (''since 0.11'') A [http://genshi.edgewall.org/wiki/Documentation/text-templates.html Genshi text template] snippet used to get the notification subject. |
| 50 | | * '''`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: |
| 51 | | * `SmtpEmailSender`: connects to an SMTP server (default). |
| 52 | | * `SendmailEmailSender`: runs a `sendmail`-compatible executable. |
| 53 | | |
| 54 | | Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. |
| 55 | | |
| 56 | | The following options are specific to email delivery through SMTP. |
| 57 | | * '''`smtp_server`''': SMTP server used for notification messages. |
| 58 | | * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server. |
| 59 | | * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account. |
| 60 | | * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account. |
| 61 | | * '''`use_tls`''': (''since 0.10'') Toggle to send notifications via a SMTP server using [http://en.wikipedia.org/wiki/Transport_Layer_Security TLS], such as GMail. |
| 62 | | |
| 63 | | The following option is specific to email delivery through a `sendmail`-compatible executable. |
| 64 | | * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options. |
| 65 | | |
| 66 | | === Example Configuration (SMTP) === |
| 67 | | {{{ |
| | 36 | === Configuration Options |
| | 37 | These are the available options for the `[notification]` section in trac.ini: |
| | 38 | |
| | 39 | [[TracIni(section=notification)]] |
| | 40 | |
| | 41 | === Example Configuration (SMTP) |
| | 42 | {{{#!ini |
| 87 | | === Customizing the e-mail subject === |
| 88 | | 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: |
| 89 | | {{{ |
| 90 | | $prefix #$ticket.id: $summary |
| | 62 | === Subscriber Configuration |
| | 63 | The default subscriptions are configured in the `[notification-subscriber]` section in trac.ini: |
| | 64 | |
| | 65 | [[TracIni(section=notification-subscriber)]] |
| | 66 | |
| | 67 | Each user can override these defaults in his ''Notifications'' preferences. |
| | 68 | |
| | 69 | 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. |
| | 70 | |
| | 71 | === Customizing the e-mail subject |
| | 72 | 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 text template] snippet. The default value is: |
| | 73 | {{{#!genshi |
| | 74 | ${prefix} #${ticket.id}: ${summary} |
| 248 | | You 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. |
| 249 | | |
| 250 | | == Filtering notifications for one's own changes == |
| 251 | | In Gmail, use the filter: |
| 252 | | |
| 253 | | {{{ |
| 254 | | from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)") |
| 255 | | }}} |
| 256 | | |
| 257 | | For Trac .10, use the filter: |
| 258 | | {{{ |
| 259 | | from:(<smtp_from>) (("Reporter: <username>" -Changes -Comment) OR "Changes (by <username>)" OR "Comment (by <username>)") |
| 260 | | }}} |
| 261 | | |
| 262 | | to delete these notifications. |
| 263 | | |
| 264 | | In Thunderbird, there is no such solution if you use IMAP |
| 265 | | (see http://kb.mozillazine.org/Filters_(Thunderbird)#Filtering_the_message_body). |
| 266 | | |
| 267 | | The best you can do is to set "always_notify_updater" in conf/trac.ini to false. |
| 268 | | You will however still get an email if you comment a ticket that you own or have reported. |
| 269 | | |
| 270 | | You can also add this plugin: |
| 271 | | http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin |
| 272 | | |
| 273 | | == Troubleshooting == |
| | 232 | 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. |
| | 233 | |
| | 234 | == Troubleshooting |
| 313 | | 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. |
| 314 | | |
| 315 | | 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. |
| 316 | | |
| 317 | | === ''501, 5.5.4 Invalid Address'' error === |
| 318 | | |
| 319 | | On IIS 6.0 you could get a |
| 320 | | {{{ |
| 321 | | Failure sending notification on change to ticket #1: SMTPHeloError: (501, '5.5.4 Invalid Address') |
| 322 | | }}} |
| 323 | | in the trac log. Have a look [http://support.microsoft.com/kb/291828 here] for instructions on resolving it. |
| 324 | | |
| | 275 | 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, change the default encoding to "quoted-printable" using the `mime_encoding` option. |
| | 276 | |
| | 277 | Quoted printable encoding works better with languages that use one of the Latin charsets. For Asian charsets, stick with the Base64 encoding. |
![(please configure the [header_logo] section in trac.ini)](/shakeweb/chrome/site/your_project_logo.png){kind=logo}
