This affects base64 and quoted-printable encoded message bodies.
The encoding-parser lacks some break; statements: currently all msg are decoded as plain text. fix is trivial.
| Comment | File | Size | Author |
|---|---|---|---|
| mailarchive-base64fix.patch | 632 bytes | rgareus |
This affects base64 and quoted-printable encoded message bodies.
The encoding-parser lacks some break; statements: currently all msg are decoded as plain text. fix is trivial.
| Comment | File | Size | Author |
|---|---|---|---|
| mailarchive-base64fix.patch | 632 bytes | rgareus |
Comments
Comment #1
rgareus commentedjust add two break;s - The attached patch includes a redundant break for the default encoding. oops. :)
Comment #2
jeremy commentedThank you very much! Committed.
Comment #3
jeremy commentedThere's nothing wrong with the explicit break after the default -- it's actually good practice in case the function changes in the future and another case gets added below the default.
I'm glad you caught this silly mistake. I had reports of bad encoding happening, but didn't have a chance to track it down -- this should fix it.
Comment #4
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.