> backup MXs should be turned off (no SMTP service) until the backup MX > detects the primary MX is down, then the backup turns itself on. When it > detects the primary is on-line, it turns itself off (that's the big > picture, there are lots of details). > > It took me awhile to come to this setup. The backup MXs are nothing but > sinks of bandwidth loss and of course another spam channel, all much > worsened if the backup MX doesn't have exactly the same restrictions as the > primary MX.
Len - Interesting concept to say the least. I am intrigued as to how you accomplish that with Postfix/BSD. I assume you have a cronjob attempting to open port 25 on the primary and starting / stopping postfix as required??? What if your primary and mx mail servers are located in different datacenters and the MX is not accepting connections because it 'knows' the primary is up BUT the sending mail server elsewhere on the internet is unable to connect to the primary? Sure it will try the MX, but as stated above, the MX can see theprimary so it is not going to accept mail. I know you have done some excellent work and come up with great solutions. As a fellow postfix user I'm curious to hear more how you control this. Regards, David Gregg dgSoft Internet Services +1.949.584-1514 --- mxGuard for IMail Adds anti-spam *and* anti-virus capabilities to your IMail server. $99 unlimited domains/users. No service agreements. Download and install a free trial version today. http://www.mxGuard.com/Postmaster/FreeTrial.asp --- 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/
