On Fri, 28 Oct 2016 11:09:27 +0200, Benoit Panizzon said: > > PS: Maybe I am not supposed to send multiline prompts if a server > > greets with HELO instead of EHLO? > > Note to self, next time read RFC before sending email... > > Old RFC 821 does not state, that a reply to HELO can be multiline. > After changing my spamtrap to only send one line in reply to HELO, it > is getting a lot of spam from all over yahoo.co.jp.
What RFC 821 actually says in section 4.2:
An SMTP reply consists of a three digit number (transmitted as
three alphanumeric characters) followed by some text. The number
is intended for use by automata to determine what state to enter
next; the text is meant for the human user. It is intended that
the three digits contain enough encoded information that the
sender-SMTP need not examine the text and may either discard it or
pass it on to the user, as appropriate. In particular, the text
may be receiver-dependent and context dependent, so there are
likely to be varying texts for each reply code. A discussion of
the theory of reply codes is given in Appendix E. Formally, a
reply is defined to be the sequence: a three-digit code, <SP>,
one line of text, and <CRLF>, or a multiline reply (as defined in
Appendix E). Only the EXPN and HELP commands are expected to
result in multiline replies in normal circumstances, however
multiline replies are allowed for any command.
Note the last sentence.
pgpT84Y6uOeHL.pgp
Description: PGP signature
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
