Ticket #1484565 (closed Bugs: fixed)
bad charsets render message/subject invisible - should assume us-ascii at least
| Reported by: | memoryhole | Owned by: | thomasb |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.1-stable |
| Component: | MIME parsing | Version: | svn-trunk |
| Severity: | major | Keywords: | |
| Cc: |
Description
If a message has a bad Content-Type encoding, roundcube gives up on rendering the message entirely. The message shows up in the message list with "(no subject)" as its subject (even though it may have a correctly encoded subject). When you try to view the message, the content of the message is missing.
I can repeatably demonstrate this by taking an ordinary email message with a Content-Type header and modifying it. For example, the following header makes the message unviewable:
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
If that header is changed to:
Content-Type: TEXT/PLAIN; charset=US-ASCII
Then suddenly it becomes viewable in roundcube again. This behavior is only true of the current SVN; it doesn't happen in 0.1-rc1. In that version of roundcube, messages with unrecognized charsets appear to be assumed to be US-ASCII, and they display well.
Unfortunately, some versions of pine and other webmails (e.g. squirrelmail) spit out these malformed emails.
