https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7249
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from [email protected] --- (In reply to Mark Martinec from comment #2) > Thanks. I agree this needs decoding, although some caution is warranted, > as the result of Encode::decode("MIME-Header",...) are perl characters > (utf8 flag on), which when potentially concatenated elsewhere with > some UTF-8 encoded string (octets, non-decoded) yields doubly encoding > of UTF-8 octets, i.e. a real mojibake mess. Patch was tested by me on live spamassassin installation with "normalize_charset 1" config and at least it didn't get any perl errors during couple of months. But some hidden problems with utf8 characters/octet may occur, so the patch needs careful inspection by somebody with better knowledge of perl utf8 and spamassassin sources than me :) > Btw, the MIME encoding in the provided sample is incorrect, it breaks > the RFC 2047 section 5 requirement: This example was taken from real spam message which was created by some non-rfc-compliant software. -- You are receiving this mail because: You are the assignee for the bug.
