james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Resolved] (MIME4J-228) Quoted-printable text part without encoding has broken characters
Date Mon, 13 May 2013 12:39:15 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Oleg Kalnichevski resolved MIME4J-228.

    Resolution: Invalid


RFC 2046 specifies that in absence of an explicit Content-Type header a body part of multipart
entity is assumed be of content type "text/plain; charset=US-ASCII".

5.1.  Multipart Media Type

   the absence of a
   Content-Type header usually indicates that the corresponding body has
   a content-type of "text/plain; charset=US-ASCII".

The thing is that word 'usually' makes this statement sound less authoritative suggesting
that there might be some less usual circumstances. However it was unable to find any definitive
statement as to what the default mime type and charset should be in absence of an explicit
Content-Type header. Therefore without additional evidence to the contrary I am inclined to
presume that the current behavior of mime4j is correct. 

Having said that we could consider providing a customizable strategy to infer default charset
based on mime type and transfer encoding. Feel free to raise a improvement request for it.

> Quoted-printable text part without encoding has broken characters
> -----------------------------------------------------------------
>                 Key: MIME4J-228
>                 URL: https://issues.apache.org/jira/browse/MIME4J-228
>             Project: James Mime4j
>          Issue Type: Bug
>          Components: parser (core)
>    Affects Versions: 0.7.2
>         Environment: Windows 7 64bits
> Oracle Java 1.7.0_17
>            Reporter: Clément Denis
>         Attachments: quotedprintablewithoutencoding.mime
> The attached message is a multipart message with a single part in a quoted printable
format, but no specific charcter encoding.
> When no content encoding specified in a body part, the DefaultMessageBuilder defaults
to us-ascii. But the output of the QuotedPrintableInputStream used to decode the text is actually
ISO_8859_1 (at least in my environment).
> Quoted printable text should not depend on the encoding of the text, so the text should
be fine.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message