https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7249

--- Comment #2 from Mark Martinec <[email protected]> ---
> This is a trivial patch and won't need CLA. Committed to 4.0 and 3.4.2
> branches.
> Committed revision 1706850.
> Committed revision 1706851.

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.

Btw, the MIME encoding in the provided sample is incorrect, it breaks
the RFC 2047 section 5 requirement:

  Each 'encoded-word' MUST represent an integral number of characters.
  A multi-octet character may not be split across adjacent 'encoded-word's.

When decoded according to rules it yields:

"0LTQvtC60YPQvNC10L3RgtGLINC00LvRjyDQvtGC0LTQ" -> документы для отд�
"tdC70LAg0LrQsNC00YDQvtCyLnBkZg=="            -> �ла кадров.pdf

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to