Hi. Am Donnerstag, 11. Januar 2007 08:39 schrieb Gordon Messmer: > A backup MX's job is to accept mail when your primary system can't, but > remote sites are going to queue mail and retry delivery anyway. You're > not going to hurt site reliability by taking down you backup MX.
Two things here: 1. On your own backup-mx, YOU can control how long messages are queued and whether or when they are bounced. 2. YOU can re-deliver waiting messages when YOU want. So when you re-awake your primary mx, you just "courier flush" on the backup mx and the messages are there. > In practice, backup MXs are just spam targets these days. Most sites > that still have them don't protect them as well as their primary > systems, so that's where many spammers deliver their mail. Drop it and > concentrate your efforts on one system. You'll be happier with the > results. My solution: I have set up the backup mx system as usual and then do a "esmtpd stop". A simple script (executed once a few minutes) tests availability of the primary mx system (just connect, HELO and QUIT). If the primary seems down, "esmtpd start" gets executed. When the primary is there again, esmtpd gets stopped. That combines both, availability in case of a failure and backscatter-protection. cu, Bernd -- Wenn du eine helfende Hand brauchst - du findest sie am Ende deines rechten oder linken Arms.
pgpS1IVPL9juc.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
