>Thanks for you input, however, it is not the NIC I am concerned about it
then I'd alias multiple ip's on one NIC >is the ISP which are dropping like flies. I do not want my client to >wake up in the mornining cast of into never never land. He lives and >dies by email (and does not trust hosting). If the vulnerability being addressed is upstream, then the solution has to be "upper" stream. The "MX algorithm" says mx2 should hold the mail until mx1 comes back on-line. Here, I say mx2 immediately relays the mail to the ip of the destination mailserver, bypassing the MX algorithm and mx1. Do this : hisdomain.com. MX mx1.isp1.com. hisdomain.com. MX mx2.isp2.com. ... where each isp is simply relaying your client's mail to your client's mailserver via ip address, not via MX records. ie, you don't want mx2 to relay via MX lookup, but via ip address. That fixes the inbound problem. For the outbound, you'll have to fix your routing setup so that if the default gateway to isp1 via link1 is down, Imail's network failsover to using the default gateway to isp2 via link2. Len To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
