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.

CommentFileSizeAuthor
mailarchive-base64fix.patch632 bytesrgareus

Comments

rgareus’s picture

just add two break;s - The attached patch includes a redundant break for the default encoding. oops. :)

jeremy’s picture

Assigned: Unassigned » jeremy
Status: Needs review » Fixed

Thank you very much! Committed.

jeremy’s picture

There'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.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.