Hector Santos wrote:
From: "Bart Schaefer" <schaefer(_at_)brasslantern(_dot_)com>
} See RFC 2821 section 6, second paragraph:
}
} "If there is a delivery failure after acceptance of a message, the
} receiver-SMTP MUST formulate and mail a notification message. This
} notification MUST be sent using a null ("<>") reverse path in the
} envelope. The recipient of this notification MUST be the address
} from the envelope return path (or the Return-Path: line). "
}
} Thats pretty straight forward to me.
That's a requirement that the receiving server send the delivery failure.
It is not a requirement that the original sender accept it.
Thats a non-issue. Unrelated really. A Callerid Verification system is
not sending mail. Half the battle is solve by being able to connect or not
connect and reaching the RCTO TO: stage. It is functionally designed to
sended "mail."
Allows me to rephrase this - This is a requirement that the receiver is
required to send the delivery failure notice back to the sender. It is
not a requirement that the address for that notice should exist and be
functional, or in your case be able to reach the RCPT TO stage.
Therefore, in practice this requirement is sometimes ignored since no
one wants to be sending email to non-existant addresses anyway, and many
filtering systems for spam will not send back a failure notice.
Yakov
-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"And this too shall come to pass"
-------
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg