Changes between Version 2 and Version 3 of TracNotification


Ignore:
Timestamp:
12/10/15 08:08:01 (19 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracNotification

    v2 v3  
    1818 
    1919Alternatively, a default domain name ('''`smtp_default_domain`''') can be set in the TracIni file (see [#ConfigurationOptions Configuration Options] below). In this case, the default domain will be appended to the username, which can be useful for an "Intranet" kind of installation. 
     20 
     21When using apache and mod_kerb for authentication against Kerberos / Active Directory, usernames take the form ('''`username@EXAMPLE.LOCAL`'''). To avoid this being interpreted as an email address, add the Kerberos domain to  ('''`ignore_domains`'''). 
    2022 
    2123== Configuring SMTP Notification == 
     
    3941 * '''`use_public_cc`''': (''since 0.10'') Addresses in To: (owner, reporter) and Cc: lists are visible by all recipients (default is ''Bcc:'' - hidden copy). 
    4042 * '''`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.  
     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. 
    4548 * '''`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. 
    4649 * '''`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: 
    4750   * `SmtpEmailSender`: connects to an SMTP server (default). 
    48    * `SendmailEmailSender`: runs a `sendmail`-compatible executable. 
     51   * `SendmailEmailSender`: runs a `sendmail`-compatible executable.    
    4952 
    5053Either '''`smtp_from`''' or '''`smtp_replyto`''' (or both) ''must'' be set, otherwise Trac refuses to send notification mails. 
     
    9598=== Customizing the e-mail content === 
    9699 
    97 The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/ticket/templates`.  You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this: 
     100The notification e-mail content is generated based on `ticket_notify_email.txt` in `trac/templates`.  You can add your own version of this template by adding a `ticket_notify_email.txt` to the templates directory of your environment. The default looks like this: 
    98101 
    99102{{{ 
    100103$ticket_body_hdr 
    101104$ticket_props 
    102 #choose ticket.new 
    103   #when True 
     105{% choose ticket.new %}\ 
     106{%   when True %}\ 
    104107$ticket.description 
    105   #end 
    106   #otherwise 
    107     #if changes_body 
    108 Changes (by $change.author): 
     108{%   end %}\ 
     109{%   otherwise %}\ 
     110{%     if changes_body %}\ 
     111${_('Changes (by %(author)s):', author=change.author)} 
    109112 
    110113$changes_body 
    111     #end 
    112     #if changes_descr 
    113       #if not changes_body and not change.comment and change.author 
    114 Description changed by $change.author: 
    115       #end 
     114{%     end %}\ 
     115{%     if changes_descr %}\ 
     116{%       if not changes_body and not change.comment and change.author %}\ 
     117${_('Description changed by %(author)s:', author=change.author)} 
     118{%       end %}\ 
    116119$changes_descr 
    117120-- 
    118     #end 
    119     #if change.comment 
    120  
    121 Comment${not changes_body and '(by %s)' % change.author or ''}: 
     121{%     end %}\ 
     122{%     if change.comment %}\ 
     123 
     124${changes_body and _('Comment:') or _('Comment (by %(author)s):', author=change.author)} 
    122125 
    123126$change.comment 
    124     #end 
    125   #end 
    126 #end 
     127{%     end %}\ 
     128{%   end %}\ 
     129{% end %}\ 
    127130 
    128131--  
    129 Ticket URL: <$ticket.link> 
     132${_('Ticket URL: <%(link)s>', link=ticket.link)} 
    130133$project.name <${project.url or abs_href()}> 
    131134$project.descr 
     
    157160}}} 
    158161 
     162 
     163== Customizing e-mail content for MS Outlook == 
     164 
     165Out-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 
     167Replace the following second row in the template: 
     168{{{ 
     169$ticket_props 
     170}}} 
     171 
     172with this instead (''requires Python 2.6 or later''): 
     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 
     186The 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 /> 
     204Changes:<br /> 
     205<br /> 
     206&nbsp;&nbsp;* component: &nbsp;changset view =&gt; search system<br /> 
     207&nbsp;&nbsp;* priority: &nbsp;low =&gt; highest<br /> 
     208&nbsp;&nbsp;* owner: &nbsp;jonas =&gt; anonymous<br /> 
     209&nbsp;&nbsp;* cc: &nbsp;daniel@example.com =&gt;<br /> 
     210&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;daniel@example.com, jonas@example.com<br /> 
     211&nbsp;&nbsp;* status: &nbsp;new =&gt; assigned<br /> 
     212<br /> 
     213Comment:<br /> 
     214I'm interested too!<br /> 
     215<br /> 
     216--<br /> 
     217Ticket URL: &lt;http://example.com/trac/ticket/42&gt;<br /> 
     218My Project &lt;http://myproj.example.com/&gt;<br /> 
     219}}} 
     220}}} 
     221 
     222**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: 
     223{{{ 
     224   sel = ['Reporter', ..., 'Keywords', 'Custom1', 'Custom2'] 
     225}}} 
     226 
     227However, 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... 
     228 
     229 
    159230== Using GMail as the SMTP relay host == 
    160231 
     
    174245 
    175246Alternatively, you can use `smtp_port = 25`.[[br]] 
    176 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. 
     247You 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 [trac:comment:2:ticket:7107 #7107] for details. 
    177248  
    178249== Filtering notifications for one's own changes ==