Dairenn Lombard wrote:
Hello there!

I have a customer that has two sendmail servers and what they have been
doing is adding domains and e-mail addresses to
/etc/mail/local-mail-hosts and /etc/mail/virtusertable by hand, and
creating the exact same UNIX logins on both Linux servers.  Then, for
all of the domains set up on both boxes, the DNS is set so that the MX
record for one is set to 10 and the other is set to 20.

Now, one of those mail servers are starting to die and I am now
recommending that they switch both mail servers to Qmail Toaster.  So
here's what I want to do.

I want to set up the MX 10 server with an smtproutes file that points
all their domains to their MX 20 server, and then have them setup all
their domains and e-mail addresses on the new server.  This way, several
things can happen:

If the MX 10 server becomes busy/unavailable, the primary server at MX
20 can get the e-mail directly.  If the MX 20 server becomes
unavailable, the MX 10 server will queue messages.

My question is, is that how the MX 10 qmail server will handle e-mail
for domains that are specified in an smtproutes file?

My other question is, they want to use the MX 10 server for outoing
e-mail if their MX 20 server goes down.  How could I set up the MX 10 to
allow them to do that?  Do I need to have something setup where the
vpopmail database is periodically dumped and rsync or scp copied over to
the other server which then imports that vpopmail database for the
purposes of allowing SMTP AUTH?
Sure, rather easy. Setup the 10 MX machine so that it has the domain in it's /var/qmail/control/rcpthosts file and it will accept email for that domain, then send it off to the 20 MX machine. Putting in the smtproute will speed this up and stop DNS lookups. That's it. The second thing you ask can be tricky. Without putting all of the domains/users on that machine as well, you'd have to have them all emailing from a static IP address and just add an entry into the tcp.smtp file to allow that IP to relay. As far as how to do the failover.... You could do a DNS round-robin, but that would not be very effective. There's a couple different ways to do it, but none of them are very "clean" or easy.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to