Hi, I think that in this case, such setup is used to achieve backup MX when the network connection of the primary MX is not available.
Of course - high availability should be achieved with i.e. heart-beat configuration ! Regards, E:S -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 13. September 2007 05:48 To: [email protected] Subject: Re: [toaster] Qmail Failover Server issues Fail-over is not done with a qmail patch ;) You should look into heartbeat and other high availability solutions. > In-house we've set up a server to act as a secondary MX record to the > domains we host mail. The server then forwards these messages to the > actual mail server the domain is hosted. The goal is that, in the event > a server dies, mail is still collected and gathered, waiting to be > delivered to the proper server. The setup of qmail follows the toaster > guide. > > Because the actual mail servers are working fine - the server is > getting nothing but spam and junk emails, filling the queue is growing > to huge sizes over 117K in messages! Spamassassin is barely able to > keep up with the load, and I'm sure clamav isn't far behind. We've been > pruning the queue of messages using qmHandle, but we need something that > handles things on its own. We've also set the queue lifetime to be 12 > hours. > > Some ideas we've been comtemplation to fix the issue: > - another failover server set up the same way that handles 1/2 the > domains secondary MX records. > - some qmail patch that reject the mail if the actual server is still > online and operational > - keep failover server offline until needed > > Any suggestions on this are appreciated. Thanks. > > James G > Sr. Systems Administrator > Cavecreek Systems Administration Team > http://www.cavecreek.net <http://www.cavecreek.net/> > > 24-hour technical support: > [EMAIL PROTECTED] > 480.449.7750 > > We welcome feedback on your customer service experience. > Please send a message to [EMAIL PROTECTED] > > __________ NOD32 2526 (20070912) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com
