Alex van den Bogaerdt wrote:
out01.example.com. A 192.0.2.1
out01.example.com. MX 0 in01.example.com.
out01.example.com. TXT "v=spf1 ip4:192.0.2.1 -all"
There's no need for out01.example.com. to accept mail
(from the outside anyway). And that's what I meant.
Isn't "if it can't receive mail it has no business to
send mail" an axiom in the e-mail architecture ? If
there's a problem with a sender you'd wish to contact
them, and if that doesn't work you could block them.
Any system that includes an SMTP server supporting mail relaying or
delivery MUST support the reserved mailbox "postmaster" as a case-
insensitive local name. This postmaster address is not strictly
necessary if the server always returns 554 on connection opening (as
described in section 3.1). The requirement to accept mail for
postmaster implies that RCPT commands which specify a mailbox for
postmaster at any of the domains for which the SMTP server provides
mail service, as well as the special case of "RCPT TO:<Postmaster>"
(with no domain specification), MUST be supported.
Without "always returning 554" not accepting mail to
<postmaster> could be enough for an RFCI listing...
as an example see the old RFCI-entry listing RFCI :-)
I think the listing rules are now more pragmatic.
Frank
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to http://v2.listbox.com/member/?list_id=735