aiosmtpd icon indicating copy to clipboard operation
aiosmtpd copied to clipboard

Support for rfc1891

Open azmeuk opened this issue 5 years ago • 2 comments

Hello, I encountered some difficulties with aiosmtpd due to its lack of support for RFC1891. For instance, the following command is not recognized by aiosmtpd and return a 501 Syntax: RCPT TO: <address> message

220 bar.tld Python SMTP 1.2+
LHLO bar.tld
250 bar.tld
MAIL FROM: [email protected]
250 OK
RCPT TO:<[email protected]>
250 OK
RCPT TO:<[email protected]> ORCPT=rfc822;[email protected]
501 Syntax: RCPT TO: <address>

Is the support for RFC 1891 planed? Would you accept pull requests for that?

azmeuk avatar Jan 18 '20 19:01 azmeuk

Would you accept pull requests for that?

Of course! And, if possible, provide test cases as well.

Or, at least provide us with test scenarios and we'll implement the test cases.

pepoluan avatar Oct 22 '20 02:10 pepoluan

I encountered some difficulties with aiosmtpd due to its lack of support for RFC1891. For instance, the following command is not recognized by aiosmtpd and return a 501 Syntax: RCPT TO: <address> message

Do note that as RFC 1891 had explicitly stated:

If the server responds with code 250 to the EHLO command, and the response includes the EHLO keyword DSN, then the Delivery Status Notification extension (as described in this memo) is supported.

So if your client insisted on sending ORCPT even though aiosmtpd.SMTP never sent the DSN keyword, the problem is with your client.

Since aiosmtpd.SMTP never actually declares any support for DSN, I'll remove the "standards compliance" tag.

pepoluan avatar Jan 01 '21 07:01 pepoluan