Custom Query (332 matches)
Results (94 - 96 of 332)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #98 | invalid | RFC 3676 support breaks when content-type doesn't include delsp parameter | bas | anonymous |
| Description |
A fix for RFC 3676 support (#94), to handle the case where the user agent provides format=flowed but doesn't set the delsp param of Content-Type |
|||
| #99 | fixed | RFC 3676 support breaks when content-type doesn't include delsp parameter | bas | ben@… |
| Description |
A fix for content=flowed support, makes it work correctly when the user agent doesn't provide the delsp param in the Content-Type header. |
|||
| #100 | fixed | problems with ticket follow-up | bas | zygis@… |
| Description |
im having problems posting follow-ups to tickets from emails. email2trac works to create new tickets from email, so i dont think there's a problem there, however the follow-ups just never appear. any ideas where i can look for more clues? email2trac is working with fetchmail on a single project. here's my email2trac.conf [DEFAULT] project: /d/trac/darqenv debug: 2 umask: 022 reply_all : 1 mailto_link: 0 email_comment: > email_header: 0 trac_version: 0.11 enable_syslog : 1 alternate_notify_template: 0 verbatim_format: 0 strip_signature: 1 use_textwrap: 70 ticket_update: 1 output of fetchmail fetchmail: 1 message for trac@example.com at mail.example.com. .TD: saving email to /tmp/msg.txt TD: part1: Content-Type: text/plain TD: part1: filename: None TD: this part is not multipart TD: writing part1 (/tmp/part1) TD: saving email to /tmp/tmpEuThG_.email2trac fetchmail: reading message trac@example.com@mail.example.com:1 of 1 (1392 header octets) (149 body octets) flushed read:errno=0 |
|||
Note: See TracQuery
for help on using queries.
