On Wed, Nov 30, 2005 at 04:21:14PM +0100, Alex van den Bogaerdt wrote:
On Wed, Nov 30, 2005 at 09:51:38AM -0500, Stuart D. Gathman wrote:
system might perform. Only if the receiver system accepts the DATA
command and the message data with a 2xx status code, should the
forwarding/relaying/proxying system "accept" the message vis-a-vis the
calling system. (Or of course if the receiver system isn't reachable.)
As a backup MX, you might consider accepting the message only when the
reciever
system *isn't* reachable, rejecting the rcpt envelope with 4xx when it *is*
reachable. Normal senders should use the primary MX when available.
Only spammers will try a backup MX first, hoping for weaker spam
defenses.
Unfortunately it is hard, if not impossible, to determine that the
sender cannot reach the primary MX. The best you can achieve
is to determine that at the moment you check, the primary MX can
reach the sender. In order to do this you need to verify the
connection between primary MX and the sender, not between backup
MX and primary MX.
also, if your objective in having a secondary mx is availability,
I imagine any failover will have some latency during which you
are not available.
since your only returning a 4xx, its not the end of the world,
but it could add to the delivery time of such mail.
Regards,
Paddy
--
Perl 6 will give you the big knob. -- Larry Wall
-------
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/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com