On 2016-07-04 11:16, Ralf Hildebrandt wrote:
Using SpamAssassin version 3.4.1 on Ubuntu precise (14.04)

My /etc/mail/spamassassin/local.cf has:

use_txrep                    1
normalize_charset            1
txrep_factory                Mail::SpamAssassin::SQLBasedAddrList
user_awl_dsn                 DBI:mysql:spamassassin:127.0.0.1
user_awl_sql_username        root
user_awl_sql_password        secret
user_awl_sql_table           txrep

My /etc/mail/spamassassin/v341.pre contains:

loadplugin Mail::SpamAssassin::Plugin::TxRep

Yet I'm seeing no entries in the sql database:

# mysql -uroot -psecret
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 80
Server version: 5.5.49-MariaDB-1ubuntu0.14.04.1 (Ubuntu)

Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> use spamassassin;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [spamassassin]> select * FROM txrep;
Empty set (0.04 sec)

SpamAssassin is used from within amavisd-new; it seems that the config is being 
read/used:

# su - amavis
$ spamassassin --lint -D 2>&1 | fgrep -i txrep
Jul  4 11:15:18.924 [17820] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::TxRep from @INC
Jul  4 11:15:18.934 [17820] dbg: TxRep: new object created
Jul  4 11:15:19.247 [17820] dbg: config: fixed relative path: 
/var/lib/spamassassin/3.004001/updates_spamassassin_org/60_txrep.cf
Jul  4 11:15:19.247 [17820] dbg: config: using 
"/var/lib/spamassassin/3.004001/updates_spamassassin_org/60_txrep.cf" for 
included file
Jul  4 11:15:19.247 [17820] dbg: config: read file 
/var/lib/spamassassin/3.004001/updates_spamassassin_org/60_txrep.cf
Jul  4 11:15:20.212 [17820] dbg: plugin: 
Mail::SpamAssassin::Plugin::TxRep=HASH(0x4ea0c08) implements 'learner_new', 
priority 0
Jul  4 11:15:20.553 [17820] dbg: TxRep: no scan in lint mode, quitting


Try enabling debug logging for plugins TxRep and auto-whitelist.

Amavis will log SA debug messages at log level 3.

amavisd.conf:
  $log_level = 3;  # or higher
  $sa_debug = 'TxRep,auto-whitelist';

make sure syslogd is not filtering out debug level messages,
then reload amavisd and grep through the log:

  tail -f /var/log/amavisd-debug.log | egrep '(TxRep|auto-whitelist): '


Mark

Reply via email to