| 42 | | * '''`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: |
| 43 | | * `base64`: default value, works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| 44 | | * `qp` or `quoted-printable`: best for european languages (more compact than base64), not recommended for non-ASCII text (less compact than base64) |
| 45 | | * `none`: no encoding. Use with plain english only (ASCII). E-mails with non-ASCII chars won't be delivered. |
| | 45 | * '''`ignore_domains`''': Comma-separated list of domains that should not be considered part of email addresses (for usernames with Kerberos domains). |
| | 46 | * '''`mime_encoding`''': (''since 0.10'') This option allows selecting the MIME encoding scheme. Supported values: |
| | 47 | * `none`: default value, uses 7bit encoding if the text is plain ASCII, or 8bit otherwise. |
| | 48 | * `base64`: works with any kind of content. May cause some issues with touchy anti-spam/anti-virus engines. |
| | 49 | * `qp` or `quoted-printable`: best for european languages (more compact than base64) if 8bit encoding cannot be used. |
| | 164 | |
| | 165 | == Customizing e-mail content for MS Outlook == |
| | 166 | |
| | 167 | 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]. |
| | 168 | |
| | 169 | Replace the following second row in the template: |
| | 170 | {{{ |
| | 171 | $ticket_props |
| | 172 | }}} |
| | 173 | |
| | 174 | with this instead (''requires Python 2.6 or later''): |
| | 175 | {{{ |
| | 176 | -------------------------------------------------------------------------- |
| | 177 | {% with |
| | 178 | pv = [(a[0].strip(), a[1].strip()) for a in [b.split(':') for b in |
| | 179 | [c.strip() for c in |
| | 180 | ticket_props.replace('|', '\n').splitlines()[1:-1]] if ':' in b]]; |
| | 181 | sel = ['Reporter', 'Owner', 'Type', 'Status', 'Priority', 'Milestone', |
| | 182 | 'Component', 'Severity', 'Resolution', 'Keywords'] %}\ |
| | 183 | ${'\n'.join('%s\t%s' % (format(p[0]+':', ' <12'), p[1]) for p in pv if p[0] in sel)} |
| | 184 | {% end %}\ |
| | 185 | -------------------------------------------------------------------------- |
| | 186 | }}} |
| | 187 | |
| | 188 | 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. |
| | 189 | {{{#!div style="margin: 1em 1.75em; border:1px dotted" |
| | 190 | {{{#!html |
| | 191 | #42: testing<br /> |
| | 192 | --------------------------------------------------------------------------<br /> |
| | 193 | <table cellpadding=0> |
| | 194 | <tr><td>Reporter:</td><td>jonas@example.com</td></tr> |
| | 195 | <tr><td>Owner:</td><td>anonymous</td></tr> |
| | 196 | <tr><td>Type:</td><td>defect</td></tr> |
| | 197 | <tr><td>Status:</td><td>assigned</td></tr> |
| | 198 | <tr><td>Priority:</td><td>lowest</td></tr> |
| | 199 | <tr><td>Milestone:</td><td>0.9</td></tr> |
| | 200 | <tr><td>Component:</td><td>report system</td></tr> |
| | 201 | <tr><td>Severity:</td><td>major</td></tr> |
| | 202 | <tr><td>Resolution:</td><td> </td></tr> |
| | 203 | <tr><td>Keywords:</td><td> </td></tr> |
| | 204 | </table> |
| | 205 | --------------------------------------------------------------------------<br /> |
| | 206 | Changes:<br /> |
| | 207 | <br /> |
| | 208 | * component: changset view => search system<br /> |
| | 209 | * priority: low => highest<br /> |
| | 210 | * owner: jonas => anonymous<br /> |
| | 211 | * cc: daniel@example.com =><br /> |
| | 212 | daniel@example.com, jonas@example.com<br /> |
| | 213 | * status: new => assigned<br /> |
| | 214 | <br /> |
| | 215 | Comment:<br /> |
| | 216 | I'm interested too!<br /> |
| | 217 | <br /> |
| | 218 | --<br /> |
| | 219 | Ticket URL: <http://example.com/trac/ticket/42><br /> |
| | 220 | My Project <http://myproj.example.com/><br /> |
| | 221 | }}} |
| | 222 | }}} |
| | 223 | |
| | 224 | **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: |
| | 225 | {{{ |
| | 226 | sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2'] |
| | 227 | }}} |
| | 228 | |
| | 229 | 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... |
| | 230 | |
| | 231 | |
