| 24 | | * '''always_notify_reporter''': Always send notifications to any address in the reporter field. |
| | 29 | * '''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 |
| | 30 | * '''smtp_subject_prefix''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default. |
| | 31 | * '''always_notify_reporter''': Always send notifications to any address in the reporter field (default: false). |
| | 32 | * '''always_notify_owner''': (''since 0.9'') Always send notifications to the address in the owner field (default: false). |
| | 33 | * '''always_notify_updater''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true). |
| | 34 | * '''use_public_cc''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). |
| | 35 | * '''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. |
| | 36 | * '''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. |
| | 37 | * '''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: |
| | 38 | * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| | 39 | * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) |
| | 40 | * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. |
| | 80 | |
| | 81 | == Using GMail as the SMTP relay host == |
| | 82 | |
| | 83 | Use the following configuration snippet |
| | 84 | {{{ |
| | 85 | [notification] |
| | 86 | smtp_enabled = true |
| | 87 | use_tls = true |
| | 88 | mime_encoding = base64 |
| | 89 | smtp_server = smtp.gmail.com |
| | 90 | smtp_port = 587 |
| | 91 | smtp_user = user |
| | 92 | smtp_password = password |
| | 93 | }}} |
| | 94 | |
| | 95 | where ''user'' and ''password'' match an existing GMail account, ''i.e.'' the ones you use to log in on [http://gmail.com] |
| | 96 | |
| | 97 | Alternatively, you can use `smtp_port = 25`.[[br]] |
| | 98 | 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. |
| | 99 | |
| | 100 | == Filtering notifications for one's own changes == |
| | 101 | In Gmail, use the filter: |
| | 102 | |
| | 103 | {{{ |
| | 104 | from:(<smtp_from>) (("Reporter: <username>" -Changes) OR "Changes (by <username>)") |
| | 105 | }}} |
| | 106 | |
| | 107 | to delete these notifications. |
| | 108 | |
| | 109 | == Troubleshooting == |
| | 110 | |
| | 111 | 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. |
| | 112 | |
| | 113 | 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. |
| | 114 | |
| | 115 | === ''Permission denied'' error === |
| | 116 | |
| | 117 | Typical error message: |
| | 118 | {{{ |
| | 119 | ... |
| | 120 | File ".../smtplib.py", line 303, in connect |
| | 121 | raise socket.error, msg |
| | 122 | error: (13, 'Permission denied') |
| | 123 | }}} |
| | 124 | |
| | 125 | 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. |
| | 126 | |
| | 127 | Many users get confused when their manual attempts to contact the SMTP server succeed: |
| | 128 | {{{ |
| | 129 | telnet localhost 25 |
| | 130 | }}} |
| | 131 | The trouble is that a regular user may connect to the SMTP server, but the web server cannot: |
| | 132 | {{{ |
| | 133 | sudo -u www-data telnet localhost 25 |
| | 134 | }}} |
| | 135 | |
| | 136 | 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. |
| | 137 | |
| | 138 | Relevant ML threads: |
| | 139 | * SELinux: http://article.gmane.org/gmane.comp.version-control.subversion.trac.general/7518 |
| | 140 | |
| | 141 | === ''Suspected spam'' error === |
| | 142 | |
| | 143 | Some SMTP servers may reject the notification email sent by Trac. |
| | 144 | |
| | 145 | 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. |
| | 146 | |
| | 147 | 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. |
| | 148 | |
