On 11/04/2015 04:27 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
>
> > +email.Charset.add_charset('utf-8',
> > + email.Charset.SHORTEST,
> > + email.Charset.QP,
> > + 'utf-8')
>
> I don't know if this actually is available, let alone whether it would
> work (might affect headers, too, and of course elderly recipient
> systems might throw a tantrum), but how about Content-Transfer-Encoding
> of 8bit?
I did test it and it does work. I didn't think of it at the time, but
replacing the body encoding (email.Charset.QP in the above patch) with
None, i.e.
email.Charset.add_charset('utf-8',
email.Charset.SHORTEST,
None,
'utf-8')
also works and produces a message with
Content-Transfer-Encoding: 8bit
It doesn't affect headers. The arguments are character set, header
encoding, body encoding, output codec. The only thing the add_charset in
the patch changes from the default is the body encoding argument.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
