Blair Harrison wrote:
On 8/29/07, Don Stokes
wrote: I've always advised that if a secondary MX host isn't going to do anything useful with incoming mail other than re-queue it for delivery, then just don't bother.
-- don
I'd have to wholeheartedly agree with that. Back when I did run a secondary, it had to do even more strict spam filtering than the primary mail server, as we'd often see spammers sending mail to the secondary mail server only, so they obviously think this is a great attack vector. Usually mail coming in from a secondary wouldn't be scrutinised anywhere near as much as mail coming from an external mail source.
And I'd have to agree to disagree. :) At least, I agree in principle, but we have a useful case for having one. We use a single 2MX for all our clients. It allows us to notice quickly when a client is having mail issues at their site and thus be proactive in fixing them, and it also allows us to dequeue often urgent email after service restoration rather than wait for the MTA's normal retry interval. It's gotten us many a "thank you for the excellent service" from our generally pretty happy client base. Anyway, not that I am pushing 2MXes as a good idea, just saying that there are some good cases for having them in some situations. Cheers, Greig McGill