Redundant Mail System Suggestions

UxBoD uxbod at
Tue Nov 27 18:35:26 GMT 2007

Hey Johnny,

Personal I would go with the primary and secondary MX record solution.  Multiple A records are find but IMHO are more used for load balancing than redundancy.

I presume MySQL will be used for MailWatch and SpamAssassin and then replicated, but you could look at storing the MS configuration withing LDAP (never tried this myself).

If you are looking for a groupware solution I personally would recommend Zimbra . They have both a OSS version (what I am using here) and a commercial version.  Outlook plugins etc.  As standard it uses a Ajax full featured web interface and is superb.


--[ UxBoD ]--
// PGP Key: "curl -s | gpg --import"
// Fingerprint: C759 8F52 1D17 B3C5 5854  36BD 1FB1 B02F 5DB5 687B
// Keyserver: Key-ID: 0x5DB5687B
// Phone: +44 845 869 2749 SIP Phone: uxbod at

----- Original Message -----
From: "Johnny Stork" <stork at>
To: mailscanner at
Sent: Tuesday, November 27, 2007 6:20:22 PM (GMT) Europe/London
Subject: Redundant Mail System Suggestions

I am working with a client seeking redundant mail and dns services so 
have been trying to come up with some suggested architectures.

client has dual internet connections. So my first thought was create two 
identical MS/MW (mailscanner/mailwatch) systems, and assign each a 
different MX record with one being higher priority than the other. The 
machine running MS/MW would also be a DNS server so what would be the 
best way to setup some redundancy for both DNS and incoming mail?

Primary MX Record (Internet connection 1)
Secondary MX Record (Internet connection 2)

What are the benefits/differences between creating a  single A record 
with the same hostname, but the two different IP's above, versus 
multiple MX records but all with the same/different priority? Or, just 
list the machines as seperate MX records with the same priority?

The next step is how to I ensure that the MS/MW systems on both servers 
remain synchronized? I can easily point them to a common Mysql database 
which will be running internally and will be redundant by way of a RH HA 
Cluster, but what about the mail user accounts? The client will be 
running an internal groupware solution, possibly Scalix, so all mail 
coming in to the gateway MS/MW servers will simple get forwarded with a 
mailertable entry so is there any need to synchronise anything else 
between the two gateway MW/MS servers?

If anyone has any other suggestions/ideas for setting up such an 
environment I would be greatful.

*Johnny Stork*
Business & Technology Consultant
stork at

MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website! 

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the MailScanner mailing list