You can try a test. Pick 10 domains and add local dns or change the mailserver in a way so they route to a host with a closed port 25.
Wait 7 hours. Revert your changes. Did all email eventually go through? Chances are a strong yes. You can always add MX 2 to point to an IP that is the same machine as MX 1 also. If MX 1 really goes down, you can bring on a store only MX at a quick moments notice. As soon as MX 1 in repaired, just xfer your mail queue over and it will be resent. There's also enough people on this list that would happily relay smtp for a few days if you needed it. Lots of options. If one can not get a mostly functioning MX back online in a few hours, you probably have network issues much higher up the chain and out of your control anyway. Some of the anti spam tactics for MX's are pretty interesting, and useful as honeypots. I'm considering a global set of MX pref 20,30,40 and 50 all as honeypots. Ips would go to rbldnsd bl zone for ASSP users. -- Scott (Sent from a mobile device) On Dec 19, 2009, at 2:05 PM, Greybear <[email protected]> wrote: > I'm glad to have your opinions on secondary MX-es. I think I'll try to > slowly convince our top brain... > > > 2009/12/19 Scott Haneda <[email protected]> > >> On Dec 19, 2009, at 12:32 AM, Paul Whelan wrote: >> >>> On 18 Dec 2009 at 14:56, Scott Haneda wrote: >>> >>>> Exactly what I usually do. Some DNS checkers run full MTA tests >>>> against both MX's. I >>>> Don't like those DNS checkers :) >>> >>> Agreed - dnsstuff and the like should move with the times. MX backup >>> is rarely an essential these days. >> >> Try http://www.intodns.com/ it is too slow, and their response on >> glue >> records is just plain wrong. I have not received an email or twitter >> reply from anyone as of yet. Probably time to make telnet and dig >> command arsenal and do this right, and really listen to the community >> about what they thing. >> -- >> Scott * If you contact me off list replace talklists@ with scott@ * >> >> >> >> --- >> --- >> --- >> --------------------------------------------------------------------- >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast >> and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Assp-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/assp-user >> > --- > --- > --- > --------------------------------------------------------------------- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast > and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
