| 28 | | * '''`smtp_enabled`''': Enable email notification. |
| 29 | | * '''`smtp_from`''': Email address to use for ''Sender''-headers in notification emails. |
| 30 | | * '''`smtp_from_name`''': Sender name to use for ''Sender''-headers in notification emails. |
| 31 | | * '''`smtp_replyto`''': Email address to use for ''Reply-To''-headers in notification emails. |
| 32 | | * '''`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. |
| 33 | | * '''`smtp_always_cc`''': List of email addresses to always send notifications to. ''Typically used to post ticket changes to a dedicated mailing list.'' |
| 34 | | * '''`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 |
| 35 | | * '''`smtp_subject_prefix`''': (''since 0.10.1'') Text that is inserted before the subject of the email. Set to "!__default!__" by default. |
| 36 | | * '''`always_notify_reporter`''': Always send notifications to any address in the reporter field (default: false). |
| 37 | | * '''`always_notify_owner`''': (''since 0.9'') Always send notifications to the address in the owner field (default: false). |
| 38 | | * '''`always_notify_updater`''': (''since 0.10'') Always send a notification to the updater of a ticket (default: true). |
| 39 | | * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). |
| 40 | | * '''`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. |
| 41 | | * '''`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: |
| 42 | | * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| 43 | | * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) |
| 44 | | * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. |
| 45 | | * '''`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. |
| 46 | | * '''`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: |
| 47 | | * `SmtpEmailSender`: connects to an SMTP server (default). |
| 48 | | * `SendmailEmailSender`: runs a `sendmail`-compatible executable. |
| 49 | | |
| 50 | | Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. |
| 51 | | |
| 52 | | The following options are specific to email delivery through SMTP. |
| 53 | | * '''`smtp_server`''': SMTP server used for notification messages. |
| 54 | | * '''`smtp_port`''': (''since 0.9'') Port used to contact the SMTP server. |
| 55 | | * '''`smtp_user`''': (''since 0.9'') User name for authentication SMTP account. |
| 56 | | * '''`smtp_password`''': (''since 0.9'') Password for authentication SMTP account. |
| 57 | | * '''`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. |
| 58 | | |
| 59 | | The following option is specific to email delivery through a `sendmail`-compatible executable. |
| 60 | | * '''`sendmail_path`''': (''since 0.12'') Path to the sendmail executable. The sendmail program must accept the `-i` and `-f` options. |
| | 30 | [[TracIni(notification)]] |
| | 129 | |
| | 130 | == Customizing e-mail content for MS Outlook == |
| | 131 | |
| | 132 | Out-of-the-box, MS Outlook normally presents plain text e-mails with a variable-width font; the ticket properties table will most certainly look like a mess in MS Outlook. This can be fixed with some customization of the [#Customizingthee-mailcontent e-mail template]. |
| | 133 | |
| | 134 | Replace the following second row in the template: |
| | 135 | {{{ |
| | 136 | $ticket_props |
| | 137 | }}} |
| | 138 | |
| | 139 | with this instead (''requires Python 2.6 or later''): |
| | 140 | {{{ |
| | 141 | -------------------------------------------------------------------------- |
| | 142 | {% with |
| | 143 | pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in |
| | 144 | [c.strip() for c in |
| | 145 | ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]]; |
| | 146 | sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone', |
| | 147 | 'Component', 'Severity', 'Resolution', 'Keywords'] %}\ |
| | 148 | ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)} |
| | 149 | {% end %}\ |
| | 150 | -------------------------------------------------------------------------- |
| | 151 | }}} |
| | 152 | |
| | 153 | The table of ticket properties is replaced with a list of a selection of the properties. A tab character separates the name and value in such a way that most people should find this more pleasing than the default table, when using MS Outlook. |
| | 154 | {{{#!div style="margin: 1em 1.75em; border:1px dotted" |
| | 155 | {{{#!html |
| | 156 | #42: testing<br /> |
| | 157 | --------------------------------------------------------------------------<br /> |
| | 158 | <table cellpadding=0> |
| | 159 | <tr><td>Reporter:</td><td>jonas@example.com</td></tr> |
| | 160 | <tr><td>Owner:</td><td>anonymous</td></tr> |
| | 161 | <tr><td>Type:</td><td>defect</td></tr> |
| | 162 | <tr><td>Status:</td><td>assigned</td></tr> |
| | 163 | <tr><td>Priority:</td><td>lowest</td></tr> |
| | 164 | <tr><td>Milestone:</td><td>0.9</td></tr> |
| | 165 | <tr><td>Component:</td><td>report system</td></tr> |
| | 166 | <tr><td>Severity:</td><td>major</td></tr> |
| | 167 | <tr><td>Resolution:</td><td> </td></tr> |
| | 168 | <tr><td>Keywords:</td><td> </td></tr> |
| | 169 | </table> |
| | 170 | --------------------------------------------------------------------------<br /> |
| | 171 | Changes:<br /> |
| | 172 | <br /> |
| | 173 | * component: changset view => search system<br /> |
| | 174 | * priority: low => highest<br /> |
| | 175 | * owner: jonas => anonymous<br /> |
| | 176 | * cc: daniel@example.com =><br /> |
| | 177 | daniel@example.com, jonas@example.com<br /> |
| | 178 | * status: new => assigned<br /> |
| | 179 | <br /> |
| | 180 | Comment:<br /> |
| | 181 | I'm interested too!<br /> |
| | 182 | <br /> |
| | 183 | --<br /> |
| | 184 | Ticket URL: <http://example.com/trac/ticket/42><br /> |
| | 185 | My Project <http://myproj.example.com/><br /> |
| | 186 | }}} |
| | 187 | }}} |
| | 188 | |
| | 189 | **Important**: Only those ticket fields that are listed in `sel` are part of the HTML mail. If you have defined custom ticket fields which shall be part of the mail they have to be added to `sel`, example: |
| | 190 | {{{ |
| | 191 | sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2'] |
| | 192 | }}} |
| | 193 | |
| | 194 | However, it's not as perfect as an automatically HTML-formatted e-mail would be, but presented ticket properties are at least readable by default in MS Outlook... |
| | 195 | |
| | 196 | |
