Urls in first line of plain text email are interpreted as headers about aenetmail HOT 3 CLOSED

Yeah, I was afraid something like that would happen. The reason that it tries to detect if he line is a header instead of assuming all lines before two line breaks are headers is because I was trying to handle a case where headers had incorrect breaks -- 2 between each.

Instead of trying to detect a header, it should detect the spacing. I'll work on that tonight.

On Dec 6, 2011, at 8:53 AM, "Waldo2k2" [email protected] wrote:

The existence of the colon in the url causes the library to assume the line is a header if it's the first non-empty line in the body of the email. Is there a better way we could be determining if the current line being parsed contains a header?

---

Reply to this email directly or view it on GitHub:
#9

from aenetmail.

Any progress on this issue? We've worked around it for now, just curious if you came up with another method for parsing the headers.

from aenetmail.

Sorry about that, I got side tracked. :] I've just published a fix for the header issue. It will now follow standard and assume that a blank line is the end of headers instead of trying to handle a rare edge-case when the header line-endings are mangled.

Andy

-----Original Message-----
From: Waldo2k2 [mailto:[email protected]]
Sent: Wednesday, December 28, 2011 8:47 PM
To: Andy Edinborough
Subject: Re: [aenetmail] Urls in first line of plain text email are interpreted as headers (#9)

Any progress on this issue? We've worked around it for now, just curious if you came up with another method for parsing the headers.

Reply to this email directly or view it on GitHub:
#9 (comment)

from aenetmail.