| Summary | IMP not parsing email headers correctly |
| Queue | IMP |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | rene (at) wherezit (dot) com |
| Created | 01/19/2011 (5315 days ago) |
| Due | |
| Updated | 04/22/2014 (4126 days ago) |
| Assigned | |
| Resolved | 01/19/2011 (5315 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ IMP not parsing email headers correctly
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
they've been sent are coming through as gibberish. Namely, they can't
read HTML and IMP is presenting the HTML email as text instead of HTML.
I'm guessing that the problem lies with parsing the line continuation
character in the email headers. The spec (RFC 822, section 3.4.2)
says that it can be either a space or a tab. I'm using spaces but
every example I've seen recently of MIME/HTML formatted emails uses
tabs.
So my belief is that IMP is only accepting tabs when it parses the
MIME email headers.
I've changed my code to use tabs to fix the immediate problem.
Sorry, I don't have the time to download/install/test/verify that this
is the problem with IMP.