On 07/09/2014 12:40 AM, RW wrote:
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.
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-on
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 re
On 07/08/2014 09:48 PM, ML mail wrote:
Hello,
I would like to run SpamAssassin on my backup MX as well in order to
avoid spam and backscatter. My backup MX will have a similar setup
and configuration as my main MX, that would be
Postfix+amavisd-new+ClamAV+SpamAssassin.
Now I have all my user c
My backup MX will be on located on another continent this is the main reason
(latency) why I would like a local read-only replica of my database on the
backup MX server.
On Tuesday, July 8, 2014 9:57 PM, Antony Stone
wrote:
On Tuesday 08 July 2014 at 21:48:58, ML mail wrote:
> Hello,
>
Hello,
I would like to run SpamAssassin on my backup MX as well in order to avoid spam
and backscatter. My backup MX will have a similar setup and configuration as my
main MX, that would be Postfix+amavisd-new+ClamAV+SpamAssassin.
Now I have all my user configuration including SpamAssassin Ba
