Hi there,
I am running two mailservers, first one serving two domains, other one
serving one domain.
Both serve as backup mx for each other. Both know about users and
aliases of the other domain(s).
On both systems, spamassassin is configured to read/store userprefs and
bayes data (per user) in a local mysql database.
Both systems reject email if the score exceeds a certain limit. To
avoid backscatter (or the need to accept any spam not rejected by the
backup mx), both servers should do their spam filtering based on
exactly the same information, including bayes data.
Now, the question is, what is the best way to share bayes data between
two (or more) servers?
I already share userprefs by setting up master-master replication
between the two mysql databases on both servers. This is uncritical,
since users (or admins) will update only userprefs for the local
virtual users on each system, which means, backup mx will never touch
primary mx userprefs.
But bayes data may be updated by either the primary mx or the backup
mx, since email may arrive at either server.
I've set up a testing environment that also uses master-master
replication of the mysql bayes database, with priority in dns set to
equal for both mx to get incoming mail distributed evenly to both
systems. So far, this seems to work, but this is a low load
environment.
Any suggestions?
Regards,
Robert
--
Robert Senger
I am running two mailservers, first one serving two domains, other one
serving one domain.
Both serve as backup mx for each other. Both know about users and
aliases of the other domain(s).
On both systems, spamassassin is configured to read/store userprefs and
bayes data (per user) in a local mysql database.
Both systems reject email if the score exceeds a certain limit. To
avoid backscatter (or the need to accept any spam not rejected by the
backup mx), both servers should do their spam filtering based on
exactly the same information, including bayes data.
Now, the question is, what is the best way to share bayes data between
two (or more) servers?
I already share userprefs by setting up master-master replication
between the two mysql databases on both servers. This is uncritical,
since users (or admins) will update only userprefs for the local
virtual users on each system, which means, backup mx will never touch
primary mx userprefs.
But bayes data may be updated by either the primary mx or the backup
mx, since email may arrive at either server.
I've set up a testing environment that also uses master-master
replication of the mysql bayes database, with priority in dns set to
equal for both mx to get incoming mail distributed evenly to both
systems. So far, this seems to work, but this is a low load
environment.
Any suggestions?
Regards,
Robert
--
Robert Senger