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