upgrading 3.0.1.1 -> 3.0.1.2->3.0.1.3 spamassassin Bayes Database ERR
Posted: 06 Sep 2016 19:11
Hi
on upgrading from 3.0.1.1 to 3.0.1.2. and 3.0.1.3 ( to solve the clamav mtagroup issue) the spam.assassin.prefs.conf file disappeared.
This could be a valid change, however Bayes stopped working, so it looks like a bug to me.
The new /etc/MailScanner/spamassassin.conf somehow only contains the last few lines from the original spam.assassin.prefs.conf file
the upgade log for 3.0.1.2 showed some erors ( I quess the .rpmsave extension was causing this )
and the MailScanner.cf not found
the Upgrade to 3.0.1.3 reported no errors:
Check link:
root root 34 Sep 6 15:27 MailScanner.cf -> /etc/MailScanner/spamassassin.conf
By restoring the original spam.assassin.prefs.conf to /etc/MailScanner/spamassassin.conf it worked again.
The easy way to check is via the tools/links->SpamAssassin Database Bayes Info. A empty screen means you should restore the spamassassin.conf and restart MailScanner.
Check:
on upgrading from 3.0.1.1 to 3.0.1.2. and 3.0.1.3 ( to solve the clamav mtagroup issue) the spam.assassin.prefs.conf file disappeared.
This could be a valid change, however Bayes stopped working, so it looks like a bug to me.
The new /etc/MailScanner/spamassassin.conf somehow only contains the last few lines from the original spam.assassin.prefs.conf file
Code: Select all
txrep_factory Mail::SpamAssassin::SQLBasedAddrList
txrep_track_messages 0
user_awl_sql_override_username TxRep
user_awl_sql_table txrep
use_txrep 0
and the MailScanner.cf not found
Code: Select all
Could not read file /usr/share/MailScanner/reports/en/stored.virus.message.txt at /usr/share/MailScanner/perl/MailScanner/Config.pm line 2856
Error in line 1341, file "/usr/share/MailScanner/reports/en/stored.virus.message.txt" for storedvirusmessage does not exist (or can not be read) at /usr/share/MailScanner/perl/MailScanner/Config.pm line 3058
MailScanner started with process id 9741
grep: /etc/mail/spamassassin/MailScanner.cf: No such file or directory
3.0.1.2 update is completeCheck link:
Code: Select all
ls -l /etc/mail/spamassassin/MailScanner.cfBy restoring the original spam.assassin.prefs.conf to /etc/MailScanner/spamassassin.conf it worked again.
The easy way to check is via the tools/links->SpamAssassin Database Bayes Info. A empty screen means you should restore the spamassassin.conf and restart MailScanner.
Check:
Code: Select all
spamassassin --lint -D
MailScanner --lint --debug
