>...
>> RFC 2821 Section 4.1.4 Order of Commands
>> ...
>> An SMTP server MAY verify that the domain name parameter in the EHLO
>> command actually corresponds to the IP address of the client.
>> However, the server MUST NOT refuse to accept a message for this
>> reason if the verification fails: the information about verification
>> failure is for logging and tracing only.
>> ...
>>
>> It can mean whatever you like (do note "MAY" and "MUST NOT" though).
>
>It just mean you can't drop a message based solely on the parameter of the
>EHLO command. You MAY check it, if you like to. But you MUST NOT drop it.
>
>
>>
>> Paul Shupak
>> [EMAIL PROTECTED]
>
>
>
I did say it could mean whatever you wanted:-)
It says nothing about dropping any message. It says only that
you "MUST NOT refuse to accept a message" because the EHLO argument doesn't
match the client's IP - read later in the same document that you could always:
550 I do not like you.
And as long as the cause above was not the reason, the clause above would
not be violated. I'll leave for another day and another argument whether
or not if the cause above contributed to a weighted system, and the message
would not have otherwise been refused, it would be a violation of either the
letter or spirit of the RFC to reject it (if it would have been rejected for
another reason or set of reasons, the argument is moot). Oh, and no RFC says
your "administrative policies" have to be reasonable or even rational (i.e.
you can be an idiot, yet still not violate any RFC - no implications about
anyone in particular:).
Dropping a message is always to be avoided (the valid reasons are
mostly the causes for DSNs that are not controversial). Free free to drop,
mark-up, deliver by avian carrier or quarantene any messages you choose,
except maybe some of those to role accounts (and that's a separate argument
too).
Paul Shupak
[EMAIL PROTECTED]
