james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Created] (MIME4J-260) MboxIterator does not handle mixed encodings
Date Thu, 16 Mar 2017 23:08:41 GMT
Sebb created MIME4J-260:
---------------------------

             Summary: MboxIterator does not handle mixed encodings
                 Key: MIME4J-260
                 URL: https://issues.apache.org/jira/browse/MIME4J-260
             Project: James Mime4j
          Issue Type: Bug
            Reporter: Sebb


As far as I can tell, some mbox files can contain messages in multiple different encodings/charsets.

This can happen if the Content-Transfer-Encoding is 8BIT, in which case the text body may
be in any encoding.

In this case, it does not make sense to decode the mbox contents before returning it to the
caller.

It might be better for the iterator to return a javax.mail.util.SharedFileInputStream
for the individual messages within the mbox.

These can then be split further into message parts.

Once the message parts have been identified, it is then possible to determine  what charset
was used so the part content can be decoded properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message