Hello,
I tried the following [1]:
C:EHLO [192.0.2.1]
S:250-ietfa.amsl.com
S:250-PIPELINING
S:250-SIZE 67108864
S:250-ETRN
S:250-STARTTLS
S:250-AUTH PLAIN LOGIN
S:250-AUTH=PLAIN LOGIN
S:250-ENHANCEDSTATUSCODES
S:250 8BITMIME
C:MAIL FROM:<>
S:250 2.1.0 Ok
C:RCPT TO:<ietf-bounces(_at_)ietf(_dot_)org>
S:550 5.7.1 <[192.0.2.1]>: Helo command rejected: RFC2821 violation
As a comment to John, Victor explained when the EHLO check is being
done in the message at
https://mailarchive.ietf.org/arch/msg/ietf/F6FfNvkLeQGcE9RdBkHWFsaTEjQ
I doubt that such filtering would, in general, catch much junk
mail. There might be a reason why it was implemented in this
case. It may not be a good time to ask about this as there was an
announcement about some upgrades to ietf.org servers.
The specification would be more lengthy if operational guidance about
such cases is included. Anyway, it would take more than that to fix
the incorrect recommendations which are available online.
Regards,
S. Moonesamy
1. The client IP address was used for the test.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp