Email Content Transfer Encoding
Replying to: I've included a patch that makes the tests pass, but as demonstrated by the patch this make us start generating email with ' Content-Transfer-Encoding: 8bit' when passing in Unicode strings as subject or content. I think that should be avoided, so I don't recommend this patch as is. The use of 8bit encoding is exactly the aim of this ticket, so the patch does the right thing IMHO. Except for a few legacy paths, SMTP is mostly 8bit today - and where not, it's the MTA's role to downconvert to 7bit. Many email clients are generating 8bit-encoded messages (Thunderbird, Mutt, etc) and people routinely use 8bit email every day.
Email Content Transfer Encoding Base64
Avoiding it makes no longer any sense, and the current practice of using quoted-printable does not work right for non-latin aplhabets. Please note that other software already implemented my proposal - see e.g.
Content Transfer Encoding Base64
Aug 27, 2016 Just noticed in the email header under the 'X-MS-Exchange' fields there's ' Content-Type: text/plain; charset='us-ascii' Content-Transfer-Encoding: quoted-printable' - So it looks like even the Exchange system my account it hosted on is receiving a plain text email?
Comments are closed.