[issue25553] SMTP.data(msg) function may cause the last CRLF of msg lost if msg is quoted-printable encoding.

Deli Zhang added the comment: I can understand you, while could you please consider below fact: Once our SMTP server module smtpd.py receives the sample mail, it will remove the end-of-data sequence, that makes the "=" become the last char of mail data. I think it's inconsistent to our SMTP cli

[issue25553] SMTP.data(msg) function may cause the last CRLF of msg lost if msg is quoted-printable encoding.

R. David Murray added the comment: RFC 2812 says: Note that the first of this terminating sequence is also the that ends the final line of the data (message text) So, smtplib is correct. If you have a server that is not respecting this, then that server is out of compliance and there isn

[issue25553] SMTP.data(msg) function may cause the last CRLF of msg lost if msg is quoted-printable encoding.

Deli Zhang added the comment: Correct the action of appending the end-of-data sequence "." -- Added file: http://bugs.python.org/file40945/smtplib.py ___ Python tracker ___ _

[issue25553] SMTP.data(msg) function may cause the last CRLF of msg lost if msg is quoted-printable encoding.

New submission from Deli Zhang: It's well known that in quoted-printable encoding the "CRLF" can be encoded to "=CRLF". For example, in attachment file test.eml, the last line is "test message.=CRLF" But after the mail is sent via SMTP and received by mail server (e.g. postfix), the last line w