Hi,
I am not sure what you think the problem is. If you are refering to the
different scores then that is to be expected as the two systems are
using different auto-whitelist databases and will probably have
different data in them.
patrickbaer wrote:
I have now came down to a problem with the auto whitelist:
See the test machine:
[4998] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in
/root/.spamassassin/auto-whitelist
[4998] dbg: auto-whitelist: db-based [EMAIL PROTECTED]|ip=190.173
scores 5/61.821
[4998] dbg: auto-whitelist: AWL active, pre-score: 2.602, autolearn score:
2.602, mean: 12.3642, IP: 190.173.128.77
[4998] dbg: auto-whitelist: add_score: new count: 6, new totscore: 64.423
[4998] dbg: auto-whitelist: DB addr list: untie-ing and unlocking
[4998] dbg: auto-whitelist: DB addr list: file locked, breaking lock
[4998] dbg: locker: safe_unlock: unlink
/root/.spamassassin/auto-whitelist.lock
[4998] dbg: auto-whitelist: post auto-whitelist score: 7.4831
Compared to the live-system:
[18824] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in
/root/.spamassassin/auto-whi
telist
[18824] dbg: auto-whitelist: db-based [EMAIL PROTECTED]|ip=190.173
scores 6/13.112
[18824] dbg: auto-whitelist: AWL active, pre-score: 2.602, autolearn score:
2.602, mean: 2.18533333
333333, IP: 190.173.128.77
[18824] dbg: auto-whitelist: add_score: new count: 7, new totscore: 15.714
[18824] dbg: auto-whitelist: DB addr list: untie-ing and unlocking
[18824] dbg: auto-whitelist: DB addr list: file locked, breaking lock
[18824] dbg: locker: safe_unlock: unlink
/root/.spamassassin/auto-whitelist.lock
[18824] dbg: auto-whitelist: post auto-whitelist score: 2.39366666666667
--
Anthony Peacock
CHIME, Royal Free & University College Medical School
WWW: http://www.chime.ucl.ac.uk/~rmhiajp/
Study Health Informatics - Modular Postgraduate Degree
http://www.chime.ucl.ac.uk/study-health-informatics/
