Modify ↓
Opened 15 years ago
Closed 15 years ago
#87 closed defect (fixed)
Doesn't work when email has '>From ' in the headers.
Reported by: | email2trac@… | Owned by: | bas |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | email2trac | Version: | 0.3 |
Keywords: | Cc: |
Description
I use procmail in explicit delivery mode to a user called email. It rewrites the 'From ' line at the start with the correct one but also copies the old one to another line just after the new one.
email2trac just drops this with no error message or anything. If I grep out '^>From ' it works as expected.
My emails look like this:
From horde@phipps-hutton.freeserve.co.uk Thu Sep 25 13:10:07 2008 >From email Thu Sep 25 13:10:07 2008 Return-Path: <horde@phipps-hutton.freeserve.co.uk> Delivered-To: unknown Received: from pop.freeserve.com (193.252.22.129) by hal.local with POP3; 25 Sep 2008 12:10:07 -0000 Message-ID: <20080925130902.x9nn00trxcoso4so@127.0.0.1> User-Agent: Horde Application Framework 3.1 Date: Thu, 25 Sep 2008 13:09:02 +0100 To: CalendarReminders: ; From: horde@phipps-hutton.freeserve.co.uk Subject: Reminder: Trac test 32 You requested to be reminded about Trac test 32, which is on 09/25/08 at 01:10pm. This is the first line. Second line. * trac markup * more markup {{{ fixed font hopefully }}} last line, bye!
Attachments (0)
Change History (2)
comment:1 Changed 15 years ago by bas
- Status changed from new to assigned
comment:2 Changed 15 years ago by bas
- Resolution set to fixed
- Status changed from assigned to closed
In trunk a message is printed when this is not a valid email format
Note: See
TracTickets for help on using
tickets.
I have done some testing and i have to add a print statement that this is not a valid email message. The python email package can not parse this email. When i comment the statenment:
I get a ticket which is unparsed, Is this what you want?