Custom Query (332 matches)
Results (25 - 27 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#92 | fixed | Possible to give examples of usage on the wiki? | anonymous | anonymous |
Description |
This sounds fantastic, but I am having trouble understanding what a user actually sends in their email when using email2trac. Is it possible to add some examples of usage, for a recommended workflow/configuration? E.g. show the emails to:
|
|||
#95 | fixed | Items being dropped or indefinately que'd by mailman when email2trac has an error | bas | anonymous |
Description |
In our syslogs we have been seeing this error: Oct 22 04:02:22 sun email2trac: Traceback (most recent call last): Oct 22 04:02:22 sun email2trac: File "/usr/local/email2trac/bin/email2trac", line 1240, in <module> tktparser.parse(sys.stdin) Oct 22 04:02:22 sun email2trac: File "/usr/local/email2trac/bin/email2trac", line 818, in parse self.new_ticket(m, spam_msg) Oct 22 04:02:22 sun email2trac: File "/usr/local/email2trac/bin/email2trac", line 719, in new_ticket self.set_reply_fields(tkt, msg) Oct 22 04:02:22 sun email2trac: File "/usr/local/email2trac/bin/email2trac", line 458, in set_reply_fields if mail_list: Oct 22 04:02:22 sun email2trac: UnboundLocalError?: local variable 'mail_list' referenced before assignment Connected to these issue we get errors similar to: Oct 24 04:02:20 sun sendmail[20474]: m9O8279H020473: to="|/usr/local/email2trac/bin/run_email2trac --project=PNIInternal --component=Tesla", ctladdr=<tesla-help@…> (47/0), delay=00:00:13, xdelay=00:00:13, mailer=prog, pri=60635, dsn=2.0.0, stat=Sent Oct 24 04:02:20 sun sendmail[20474]: m9O8279H020473: to=<lewing@…>, delay=00:00:13, xdelay=00:00:00, mailer=esmtp, pri=60635, relay=emfw4.xxxx.zzz. [128.112.131.23], dsn=2.0.0, stat=Sent (Ok: queued as A547D904E00) This is causing some of our emails to not be processed into the ticket system. We think it's because these are emails being generated en-masse to notify us and users of their ID's expiring. It could be a timing or threading issue but we arn't quite sure what's going on. If you have any testing or suggestions we welcome them as this needs to be fixed. |
|||
#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 |