Re: [Declude.JunkMail] OT: Store and Forward Spam Filtering to Multiple IPs

[Matt]

Goran, It's a lot of work to create an extra level of complexity to handle something that is almost never an issue and can be resolved smoothly if there ever was. I have had a couple such requests related to this very thing from my customers, but when I explain that we spool undeliverable messages for 3 days before bouncing and that all they have to do is call and I can switch an IP for them if necessary (or they could switch the IP on their own servers without calling me), they seem to understand that this is adequate.  I think that a good deal of the concern involves what happens when they go down on a weekend and not wanting E-mail to bounce if so. Naturally I am not dealing with companies with tens of thousands of accounts who could justify such redundancy.  Even though your clients might have two gateways currently, they likely have only one mail server anyway, so there is still a single point of failure in the mix on their end.  You should just do everything that you can to make sure that you have full redundancy on your end and try to explain to them that their own gateway redundancy shouldn't be a concern and that they can save a tree by turning one of them off and keeping it as a cold spare if they wish. Matt Goran Jovanovic wrote: Would this work? Instead of using the hosts file to define the IPs and DOMAINS could you not create a zone on your own DNS server for the domain in question and then define 2 MX records? In this case when the primary goes down it will flip to the secondary by itself? Then you would not need to put it into the hosts file. Or is this not a good idea? Goran Jovanovic The LAN Shoppe -----Original Message----- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Markus Gufler Sent: Wednesday, September 28, 2005 1:38 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] OT: Store and Forward Spam Filtering to Multiple IPs ... 66.148.217.251 domain.com 70.60.133.251 domain.com will this mechanism rotate through both IPs or will it also just use whichever it hits first when reading from the top of the list down? Or is it just a bad idea in general to do this and we will just have to change the IP manually if one ISP goes down? I think this will always forward messages to the first entry, and so it will not do what you want. We've had the same request and so we've defined all our store&forward IP's in a simple database table. This database contains domains, primary and eventualy secondary MX IP's. Then we've set up our monitoring system to try to reach the primary MX on port 25. if this will fail two consecutive times the action is a simple script that does the following 1.) mark this domain in the table as fault 2.) read all active entries from the table and choose the primary MX or the secondary if marked as fault 3.) write a new hosts file 4.) stop and start the Imail smtp service If the monitoring system can see again the primary MX on port 25 there is a similar script that put's back to the primary mx this domain. Hope this helps Markus --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.