[RFCI-Discuss] HELO required
csmailreport
csmailreport at googlemail.com
Wed Dec 26 13:33:56 EST 2007
On Dec 26, 2007 7:11 PM, Ovidiu C. <ovidiu at devstudio.eu> wrote:
> My MTA requires connecting clients to send a HELO first.
> 503 5.5.1 Error: send HELO/EHLO first
> Is this a violation of any RFC? Should I drop that requirement?
>
http://www.ietf.org/rfc/rfc2821.txt
Section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO)
[Page 29]
> In any event, a
> client MUST issue HELO or EHLO before starting a mail transaction.
There's a MUST, so what you do appears to be ok and enforcing the MUST
keyword of the RFC.
I voluntarily elude the question on whether RFC 2821 is the current SMTP
standard or whether it's still RFC 821, which was written before the
MUST/SHOULD/MAY/MUST NOT keyword usage was codified.
(season's greetings btw :-)
-- N.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.megacity.org/pipermail/rfci-discuss/attachments/20071226/3af18f57/attachment.htm
More information about the RFCI-Discuss
mailing list