[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: New issue: https://bugs.python.org/issue34424 -- ___ Python tracker ___ ___ Python-bugs-list

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: check out https://devguide.python.org. (Basically, banch and generate a PR on github). And please open a new issue for this. -- ___ Python tracker

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: Thanks David: PR on Github (which is R/O) or where should I submit to? -- ___ Python tracker ___

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: Sorry, I haven't had time to look at it yet :( Not sure when I will, things are more than a bit busy for me right now. Ping me again in two weeks if I haven't responded, please. The proposed solution sounds reasonable, though, so you could also propose

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: @David, any thoughts on this? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: David, I tried to find the mentioned '\r\r…\n' issue but I could not find it here. However, from an initial investigation into the BytesGenerator, here is what’s happening. Flattening the body and attachments of the EmailMessage object works, and eventually

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: So that’s interesting. I thought that setting `international = True` (see line https://github.com/python/cpython/blob/master/Lib/smtplib.py#L947) would be a neat workaround, but the opposite. When delivering those emails to Gmail I started seeing Failed

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: > Well, posting on a closed issue is generally not the best way :) Fair enough ;) > The multiple carriage returns is a bug, and there is an open issue for it, > though I'm not finding it at the moment. Oh good, yes that should be fixed! My current

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Stéphane Wirtel added the comment: Hi David, What is the related issue with the new lines? > On 31 Jul 2018, at 15:18, R. David Murray wrote: > > > R. David Murray added the comment: > > Well, posting on a closed issue is generally not the best way :) > > The current behavior with

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: Well, posting on a closed issue is generally not the best way :) The current behavior with regards to the SMTPUTF8 flag is correct (it only matters for *addresses*, display names can already be transmitted if they contain non-ascii using non SMTPUTF8

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: (continuing the previous message msg322761) …unless the addresses should be checked separately from the display names, in which case the BytesGenerator’s flatten() function should be fixed. Without reading the RFC, please let me know how to continue from here.

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Jens Troeger added the comment: I was about to open an issue when I found this one. Consider an email message with the following: message = EmailMessage() message["From"] = Address(addr_spec="b...@foo.com", display_name="Jens Troeger") message["To"] = Address(addr_spec="f...@bar.com",

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

New submission from R. David Murray: Now that I've committed issue 24211, we can also add SMTPUTF8 support to smptlib's send_message command. See attached patch. -- files: send_message_smtputf8.patch keywords: patch messages: 243413 nosy: r.david.murray priority: normal severity:

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Changes by R. David Murray rdmur...@bitdance.com: -- components: +email nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24218 ___ ___

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Changes by Maciej Szulik solt...@gmail.com: -- nosy: +maciej.szulik ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24218 ___ ___ Python-bugs-list

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: Thanks Maciej. -- resolution: - fixed stage: patch review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24218 ___

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Roundup Robot added the comment: New changeset 30795a477f85 by R David Murray in branch 'default': #24218: Add SMTPUTF8 support to send_message. https://hg.python.org/cpython/rev/30795a477f85 -- nosy: +python-dev ___ Python tracker

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

Maciej Szulik added the comment: David one small comment regarding typo in smtplib.py, but most importantly I'd suggest adding additional test case to cover the path (the newly added one) where you get a UnicodeEncodeError upon encoding from or to with UTF8 and then failing to find SMTPUTF8

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: Oh, right, that's what I get for doing this at the end of a long chain of patch reviews :). I added that code after I'd written the test and forgot to go back and test it. -- ___ Python tracker