Message140259
| Author |
Blame-me.Jaillie |
| Recipients |
Blame-me.Jaillie |
| Date |
2011年07月13日.14:37:33 |
| SpamBayes Score |
2.451279e-07 |
| Marked as misclassified |
No |
| Message-id |
<1310567855.09.0.336758038294.issue12552@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Apologies if this is in the wrong place.
Simple enough issue. This line of code from email.mime:
MIMEText(textonly, 'plain', _charset='UTF-8')
Where 'textonly' is just a plain text email message to be displayed on a multipart message in a client that does not support HTML email.
This always results in: Content-Transfer-Encoding: BASE64
rather than allowing selection of the encoder (7 or 8 bit MIME/quoted printable). The option to set this with _encoders was removed.
This presents a couple of issues. First of all, BASE64 is not optimal for text - it adds (granted small) amounts of overhead and CPU usage. Second, commercial and O/S anti-spam scanners have rules that penalise messages solely BASE64 encoded.
As this is part of the mime email package, a simple flag to set the Content-Transfer-Encoding by hand would be help anyone trying to produce sensible email applications with Python.
Whilst my version of Python is old - I believe this issue remains in later versions. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年07月13日 14:37:35 | Blame-me.Jaillie | set | recipients:
+ Blame-me.Jaillie |
| 2011年07月13日 14:37:35 | Blame-me.Jaillie | set | messageid: <1310567855.09.0.336758038294.issue12552@psf.upfronthosting.co.za> |
| 2011年07月13日 14:37:34 | Blame-me.Jaillie | link | issue12552 messages |
| 2011年07月13日 14:37:33 | Blame-me.Jaillie | create |
|