Adam Bailey <[EMAIL PROTECTED]> wrote:
> If the headers have even minor problems, they will be relegated to
> /dev/null without warning.
If that is true, it makes AOL one of the worst e-mail providers in
the world, since it puts them in the class "intentionally unreliable".
I'm not against spam filtering, but first accepting a message for
delivery and then discarding it without warning is outright evil.
It's also a violation of a clear MUST NOT in RFC1123:
5.3.3 Reliable Mail Receipt
When the receiver-SMTP accepts a piece of mail (by sending a
"250 OK" message in response to DATA), it is accepting
responsibility for delivering or relaying the message. It must
take this responsibility seriously, i.e., it MUST NOT lose the
message for frivolous reasons, e.g., because the host later
crashes or because of a predictable resource shortage.
If there is a delivery failure after acceptance of a message,
the receiver-SMTP MUST formulate and mail a notification
message.
> * Mail servers in the Received headers which do not respond to
> reverse DNS lookups properly.
What happens in case of a timeout during the reverse DNS lookup?
-- Norbert.
