Quost schrieb:
> This may be the RFC requirement that you are looking for: RFC1123 5.2.9 > http://www.ietf.org/rfc/rfc1123.txt > "5.2.9 Command Syntax: RFC-821 Section 4.1.2 The syntax shown in RFC-821 > for the MAIL FROM: command omits the case of an empty path: "MAIL FROM: <>" > (see RFC-821 Page 15). An empty reverse path MUST be supported." Ah, I see, but I don't want to allow it... Hmmm, makes it not easier to fight Spam... > I believe it may be to do with rejected and bounced messages and return > receipts Yes (same RFC): 5.3.3 Reliable Mail Receipt [...] 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; see Section 3.6 of RFC-821. The recipient of this notification SHOULD be the address from the envelope return path (or the Return-Path: line). However, if this address is null ("<>"), the receiver-SMTP MUST NOT send a notification. If the address is an explicit source route, it SHOULD be stripped down to its final hop. Many thanks. Gerrit -- =^..^= - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
