Custom Query (332 matches)
Results (88 - 90 of 332)
| Ticket | Resolution | Summary | Owner | Reporter | |||
|---|---|---|---|---|---|---|---|
| #91 | fixed | Config file parsing issue | bas | Matthew.Carlson@… | |||
| Description |
Email2trac doesn't work with [DEFAULT] configuration. Fails with the message "No Trac project is defined in the email2trac config file." If I use the named project configuration (Ex: [bas]), and then call email2trac with the --project bas option it works fine. Maybe something changed in the config-parsing dependencies? Environment: Windows XP Python 2.5 Trac 0.11.1 Email2Trac 0.30 |
||||||
| #93 | duplicate | Attachments are added to tickets, but are broken | bas | planktr@… | |||
| Description |
I have email2trac working on a Windows server using fetchmail+Cygwin. I have also had luck with GetMail?. Messages are being retrieved from Exchange 2003 server. I've tried using POP3 and IMAP. With either tool, attachments are being created on the tickets, but they don't open. For example, an image attachment is added to the ticket, but when clicked on, the file appears as a broken image. In the trac attachments folder, there are image files that are of the expected size, but they don't open. Is there a configuration setting that would impact this? When using GetMail?, i enabled the extract option and the attachments were stored separately, so i assume the attachments are arriving with the messages, it just seems like they aren't making it through the email2trac script. Any ideas? |
||||||
| #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]:
|
||||||
