Custom Query (332 matches)
Results (277 - 279 of 332)
| Ticket | Resolution | Summary | Owner | Reporter | |||
|---|---|---|---|---|---|---|---|
| #94 | fixed | Support for RFC 3676 (format=flowed) | bas | ben@… | |||
| Description |
Most email clients wrap long lines to <80 characters. In some cases, this breaks Trac wiki formatting (when verbatim_format is off). For example: * This is a very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very long list item may get incorrectly rendered as
very very very very very very very very very very very very very very very very very very very very long list item Format=flowed property of plain-text email, specified in RFC 3676, deals with this problem. The attached patch (against email2trac 0.5) implements format=flowed support. When this patch is applied, the following should be added to [wiki/Email2tracConfiguration]:
|
||||||
| #250 | fixed | Support for trac version 0.13 | bas | simeonov@… | |||
| Description |
I was trying to setup email2trac with our new trac installation (latest development version), and new tickets were not created for the emails. Then I realized that email2trac was reporting in the syslog that trac version 0.13 is not supported. With a small patch to /usr/bin/email2trac to ignore this, now my tickets are being created (attachments are working too). Are there any reasons (known problems) for not "officially" supporting trac 0.13? -- Alexander |
||||||
| #413 | fixed | Support for Trac version 1.2 | bas | sbroadhead@… | |||
| Description |
Recently upgraded our Trac system to version 1.2 and broke our email2trac functionality. Am seeing the following in our syslog: "Mar 13 14:44:08 <tracserver> email2trac <trac_proj>: TRAC version 1.2 is not supported" <tracserver> and <trac_proj> replacements for specific values. Will Trac 1.2 be supported soon? Also... upgraded to email2trac version 2.10 |
||||||
