[issue39757] EmailMessage bad encoding for international domain

[Irit Katriel]

Irit Katriel  added the comment:

Reproduced on 3.11.

--
nosy: +iritkatriel
versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39757] EmailMessage bad encoding for international domain

[R. David Murray]

R. David Murray  added the comment:

This is not actually a duplicate of 11783.  Rereading (parts of) that issue, we 
decided we currently have no good way to do automatic conversion between 
unicode and internationalized domains, so the user of the library has to do it 
themselves.  This means that the bug *here* is that the new email API is 
*wrongly* encoding the non-ascii in the domain by using an encoded word.  I'm 
surprised at that; I thought I'd guarded against it.

What should be happening here is that an error should be raised when that 
header is set (or possibly when it is accessed/serialized, but when set would 
be better I think) saying that there is non-ascii in the domain part.

--
resolution: duplicate -> 
stage: resolved -> needs patch
status: closed -> open
superseder: email parseaddr and formataddr should be IDNA aware -> 
title: EmailMessage wrong encoding for international domain -> EmailMessage bad 
encoding for international domain

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com