Thank you, Kind Sir.
I corrected a couple of spelling errors, but otherwise that's it. I do
wonder if we might want to elaborate more, for example on setting up
secondary MX servers. And I don't think that it is right to refer to the
eventual target in that example as an internal server, but I didn't change
it because I wasn't sure what you had in mind.
What I'm thinking is something like, let's say that you wanted me to act as
a Secondary MX for parducci.net. You would simply add:
IN MX 20 mail.devtech.com.
to your zone file. On my end, I'd have to setup a <mailet> to select
messages intended for parducci.net, and run them through RemoteDelivery,
using mail.parducci.net as the gateway. When your system would be
unavailable, mine would be used to queue up messages until your server
became available again.
Load balancing is a bit different. That would be something like:
IN MX 10 mail1.parducci.net.
IN MX 10 mail2.parducci.net.
IN MX 10 mail3.parducci.net.
We would randomly select a server. An useful combination could be:
IN MX 10 mail1.parducci.net.
IN MX 10 mail2.parducci.net.
IN MX 10 mail3.parducci.net.
IN MX 20 mail.parducci.net.
All e-mail should go through mail[1,2,3], where they do front-end work,
e.g., spam filtering, and in turn forward only legitimate e-mail to the real
mail server.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
