My comment to this would be while I agree with your point, there has to be an advantage in having a local Secondary MX to catch mail being queued in locations a fair distance away? Recovery of mail delivery has gotta be faster... I had assumed that most ISPs ran both primary and secondary MX somewhere in their network, in case of failures like this one.. I guess I assumed too much of Xtra? :) Mark. At 14:08 4/09/2001 +1200, you wrote:
Mark Foster
wrote: Simons Idea of setting up some servers as Secondary MX isnt a silly idea but I need to ask the questions:
Actually, secondary MXs usually are a silly idea, if the MX can't actually do anything useful with the mail apart from queuing it. All they do is take a whole bunch of mail that would otherwise queue at the client end mail server, and put them in one big queue. It doesn't deliver the mail any faster, and if clients have their mail servers' retry timeouts screwed down so that they know in good time that their mail hasn't got through, that decision its taken away from them.
Most mailers have a hard time with huge queues of undeliverable mail, so such an MX is not going to be as efficient at dealing with the backlog when the primary comes back up as just leaving the mail where it is on client servers.
-- don --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog
--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog