This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steven.daprano
Recipients Kenny Trytek, chason.chaffin, r.david.murray, steven.daprano
Date 2018-01-25.15:18:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20180125151753.GY22500@ando.pearwood.info>
In-reply-to <1516890497.9.0.467229070634.issue32657@psf.upfronthosting.co.za>
Content
On Thu, Jan 25, 2018 at 02:28:17PM +0000, R. David Murray wrote:

> obviously I missed that mutation of the value 
> in the code review of the patch that added those lines :(

The docstring for send_message does say 

    If the sender or any of the recipient addresses contain non-ASCII
    and the server advertises the SMTPUTF8 capability, the policy is
    cloned with utf8 set to True for the serialization, and SMTPUTF8
    and BODY=8BITMIME are asserted on the send.

which I don't really understand, but I thought that perhaps it was a 
typo for *inserted* on the send, in the sense of inserted into the mail 
options:

    mail_options += ['SMTPUTF8', 'BODY=8BITMIME']

So are we agreed this is a bug? What about the default for rcpt_options 
being a dict?
History
Date User Action Args
2018-01-25 15:18:01steven.dapranosetrecipients: + steven.daprano, r.david.murray, Kenny Trytek, chason.chaffin
2018-01-25 15:18:01steven.dapranolinkissue32657 messages
2018-01-25 15:18:01steven.dapranocreate