Hi Bart,
----- Original Message -----
From: "Bart Schaefer" <schaefer(_at_)brasslantern(_dot_)com>
To: "ASRG" <asrg(_at_)ietf(_dot_)org>
} 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."
But with that said, the receiver must accept a NULL address. Its a
requirement. See RFC 1123, specifically
5.4 SMTP REQUIREMENTS SUMMARY
5.3.3 Reliable Mail Receipt
---
Hector Santos
WINSERVER "Wildcat! Interactive Net Server"
support: http://www.winserver.com
sales: http://www.santronics.com
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg