[issue34591] smtplib mixes RFC821 and RFC822 addresses

2020-03-23 Thread Manjusaka
Manjusaka added the comment: > This is a problem because not all RFC822 addresses are valid RFC821 addresses. Do you mean that we would add a verification before we send the command? -- nosy: +Manjusaka ___ Python tracker

[issue34591] smtplib mixes RFC821 and RFC822 addresses

2020-03-14 Thread Daurnimator
Daurnimator added the comment: On Sun, 15 Mar 2020 at 08:58, Ashwin Ramaswami wrote: > What do you mean by "it then proceeds to use it as an RFC821 address"? It writes it into an SMTP command as if it was an RFC821 address. This is a problem because not all RFC822 addresses are valid RFC821 a

[issue34591] smtplib mixes RFC821 and RFC822 addresses

2020-03-14 Thread Ashwin Ramaswami
Ashwin Ramaswami added the comment: What do you mean by "it then proceeds to use it as an RFC821 address"? -- nosy: +epicfaace ___ Python tracker ___ _

[issue34591] smtplib mixes RFC821 and RFC822 addresses

2018-09-05 Thread Quae Quack
New submission from Quae Quack : smtplib.sendmsg is documented to take RFC822 addresses. and e.g. if the `to_addrs` argument isn't provided then it gets the To address directly from the headers (which is in RFC822 form). However it then proceeds to use it as an RFC821 address and sends it ove