| Summary | Incorrect parsing of MIME message |
| Queue | IMP |
| Queue Version | 4.2 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | imp (at) laamanaama (dot) helsinki (dot) fi |
| Created | 09/09/2008 (6265 days ago) |
| Due | |
| Updated | 09/09/2008 (6265 days ago) |
| Assigned | |
| Resolved | 09/09/2008 (6265 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
is unable to display the alternative part. This is the first error I
have noticed.
The message contains 2 top-level multipart/alternative MIME-entities.
The second entity recursively contains MIME-parts. IMP shows the
second part as attachment icons, but only the XLS, PDF, PDF parts are
visible and the text/html part are missing.
It turns out our configuration had:
$mime_drivers['imp']['html'] = array(
'inline' => false,
Changing the value to "true" fixed the problem.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Incorrect parsing of MIME message
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
unable to display the alternative part. This is the first error I have
noticed.
The message contains 2 top-level multipart/alternative MIME-entities.
The second entity recursively contains MIME-parts. IMP shows the
second part as attachment icons, but only the XLS, PDF, PDF parts are
visible and the text/html part are missing.
I have checked out the message structure and could not find any
problems. The ancient IMP 3.x, current Thunderbird, current Pine and
current Mutt all parse it correctly.