Changes between Version 1 and Version 2 of TracNotification


Ignore:
Timestamp:
May 15, 2010, 9:05:30 PM (14 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracNotification

    v1 v2  
    1616
    1717=== 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:
     18These are the available options for the `[notification]` section in trac.ini.
     19
     20 * '''`smtp_enabled`''': Enable email notification.
     21 * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails.
     22 * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails.
     23 * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails.
     24 * '''`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.
     25 * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.''
     26 * '''`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
     27 * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default.
     28 * '''`always_notify_reporter`''':  Always send notifications to any address in the reporter field (default: false).
     29 * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false).
     30 * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true).
     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:
    3434   * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines.
    3535   * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64)
    3636   * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered.
     37 * '''`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.
     38 * '''`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:
     39   * `SmtpEmailSender`: connects to an SMTP server (default).
     40   * `SendmailEmailSender`: runs a `sendmail`-compatible executable.
    3741
    38 Either '''smtp_from''' or '''smtp_replyto''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.
     42Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails.
    3943
    40 === Example Configuration ===
     44The following options are specific to email delivery through SMTP.
     45 * '''`smtp_server`''': SMTP server used for notification messages.
     46 * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server.
     47 * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account.
     48 * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account.
     49 * '''`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.
    4150
     51The following option is specific to email delivery through a `sendmail`-compatible executable.
     52 * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options.
     53
     54=== Example Configuration (SMTP) ===
    4255{{{
    4356[notification]
     
    4861smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
    4962}}}
     63
     64=== Example Configuration (`sendmail`) ===
     65{{{
     66[notification]
     67smtp_enabled = true
     68email_sender = SendmailEmailSender
     69sendmail_path = /usr/sbin/sendmail
     70smtp_from = notifier@example.com
     71smtp_replyto = myproj@projects.example.com
     72smtp_always_cc = ticketmaster@example.com, theboss+myproj@example.com
     73}}}
     74
     75=== Customizing the e-mail subject ===
     76The 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:
     77{{{
     78$prefix #$ticket.id: $summary
     79}}}
     80The following variables are available in the template:
     81
     82 * `env`: The project environment (see [trac:source:/trunk/trac/env.py env.py]).
     83 * `prefix`: The prefix defined in `smtp_subject_prefix`.
     84 * `summary`: The ticket summary, with the old value if the summary was edited.
     85 * `ticket`: The ticket model object (see [trac:source:/trunk/trac/ticket/model.py model.py]). Individual ticket fields can be addressed by appending the field name separated by a dot, e.g. `$ticket.milestone`.
    5086
    5187== Sample Email ==
     
    74110My Project <http://myproj.example.com/>
    75111}}}
     112
     113== Using GMail as the SMTP relay host ==
     114
     115Use the following configuration snippet
     116{{{
     117[notification]
     118smtp_enabled = true
     119use_tls = true
     120mime_encoding = base64
     121smtp_server = smtp.gmail.com
     122smtp_port = 587
     123smtp_user = user
     124smtp_password = password
     125}}}
     126
     127where ''user'' and ''password'' match an existing GMail account, ''i.e.'' the ones you use to log in on [http://gmail.com]
     128
     129Alternatively, you can use `smtp_port = 25`.[[br]]
     130You 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.
     131 
     132== Filtering notifications for one's own changes ==
     133In Gmail, use the filter:
     134
     135{{{
     136from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)")
     137}}}
     138
     139to delete these notifications.
     140
     141In Thunderbird, there is no such solution if you use IMAP
     142(see http://kb.mozillazine.org/Filters_(Thunderbird)#Filtering_the_message_body).
     143
     144The best you can do is to set "always_notify_updater" in conf/trac.ini to false.
     145You will however still get an email if you comment a ticket that you own or have reported.
     146
     147You can also add this plugin:
     148http://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin
    76149
    77150== Troubleshooting ==
     
    102175}}}
    103176
    104 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.
     177In 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.
    105178
    106179Relevant ML threads:
     
    113186The 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.
    114187
    115 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.
     188Quoted 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.
    116189
    117190----