[MIME4J-230] Provide a way to override the default charset for mime parts without specified charset or no Content-Type header

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.7.2
• Component/s: parser (core)
• Assignee: Unassigned
• Reporter: Clément Denis
• Created: 21/May/13 13:38
• Updated: 21/May/13 13:38

Description

When the charset or the Content-Type header is missing from a part in a multipart message, the charset defaults to us-ascii, as it should according to RFC 2046/5.1.

For some applications (especially those dealing with non-US mime messages), this default results in broken encoding most of the time.

The default charset is hardcoded in DefaultBodyDescriptor, and cannot be easily customized. There should be a way to define this default charset.