The reason for read-only is that I am using PostgreSQL with hot standby streaming replication. The main MX server will use the master PostgreSQL server and the backup MX will use its own local PostgreSQL slave server. The slave server of a PostgreSQL hot standby pair is only available in read-only for queries, this is how PostgreSQL works for streaming replication as such the SQL queries on my slave server (the backup MX server) must be only SELECTs and such but no INSERTs.
Thanks for pointing out the use_learner parameter, which I will definitely want to 1. I guess I will have to test and see if this is doable. In the worst case the INSERT queries would fail but maybe SA can handle that properly and still work or else I simply disable Bayes on the backup MX. On Wednesday, July 9, 2014 12:40 AM, RW <[email protected]> wrote: On Tue, 8 Jul 2014 12:48:58 -0700 ML mail wrote: > Hello, > > I would like to run SpamAssassin on my backup MX as well in order to > avoid spam and backscatter. > ... > Now I have all my user configuration including SpamAssassin Bayes and > AWL stored in PostgreSQL and my backup MX will have a read-only > replica of that PostgreSQL database. So my plan would be to have SA > on the backup MX to use the Bayes+AWL data from the PostgreSQL in > read-only mode meaning that it would not write any new Bayes+AWL info > but just read it. So my question here is: is it possible to tell SA > through its config to use Bayes+AWL data in read-only mode? I can see why you'd want to use a copy, but why does it matter that it's not written to? On Tue, 08 Jul 2014 22:53:47 +0200 Axb wrote: > use_bayes 1 > use_bayes_rules 1 > use_learner 0 use_learner ( 0 | 1 ) (default: 1) Whether to use any machine-learning classifiers with SpamAssassin, such as the default 'BAYES_*' rules. Setting this to 0 will disable use of any and all human-trained classifiers. > bayes_auto_learn 0 > > that will use BAyes in read only mode. Aside from use_learner, it wouldn't turn-off atime updates. > Afaik, this will not control AWL - maybe disable that on the backup MX >
