Issue 6900 in k9mail: Bug: k9 mail should use Quoted-Printable instead of 8bit Content-Transfer-Encoding

[k9m...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Product-k9mail

New issue 6900 by fcrvinc...@gmail.com: Bug: k9 mail should use
Quoted-Printable instead of 8bit Content-Transfer-Encoding
https://code.google.com/p/k9mail/issues/detail?id=6900

Since version 2.600 K9 uses 8bit Content-Transfer-Encoding to send messages
to mail servers that support 8bit encoding.

However some servers that support the 8bit encoding do not support 8bit
encoding when they further relay emails to another gateway - for example to
a mobile email gateway.

This is the case for example of the Orange provider severs that accept 8bit
and one can read correctly 8bit encoded emails from the Orange webmail
interface - however when trying to read the same email from the
Orange "Mail Orange" mobile app the same email appears to be garbled - most
likely because the email is internally relayed to an Orange email server
that does not support 8bit encoding or performs an incorrect processing of
8bit encoded messages.

It seems that K9 should rather always use the Quoted-Printable encoding
even if 8bit encoding is supported by the recipient server.

Other email clients like Profimail correctly use the Quoted Printable
encoding in all cases.

Also the RFC about Content-Transfer-Encoding strongly discourages using
8bit encoding (see
http://www.w3.org/Protocols/rfc1341/5_Content-Transfer-Encoding.html)

Please correct this behaviour that I think can be considered as a bug.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings