Skip wrote:
How does one set the file location for the auto-whitelist file on a
3.2.x system? I am on a shared hosting system, but call spamassassin
manually from procmail. Here's the debug output that deals with
auto-whitelist:
[25947] dbg: locker: safe_lock: created
/ramdisk/etc/spamassassin/data/auto-whitelist.lock.box106.bluehost.com.25947
[25947] dbg: locker: safe_lock: trying to get lock on
/ramdisk/etc/spamassassin/data/auto-whitelist with 0 retries
[25947] dbg: locker: safe_lock: link to
/ramdisk/etc/spamassassin/data/auto-whitelist.lock: link ok
[25947] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in
/ramdisk/etc/spamassassin/data/auto-whitelist
[25947] dbg: auto-whitelist: db-based [EMAIL PROTECTED]|ip=71.113
scores 31/-157.366
[25947] dbg: auto-whitelist: AWL active, pre-score: -4.423, autolearn
score: -4.423, mean: -5.07632258064516, IP: 71.113.166.229
[25947] dbg: auto-whitelist: add_score: new count: 32, new totscore:
-161.789
[25947] dbg: auto-whitelist: DB addr list: untie-ing and unlocking
[25947] dbg: auto-whitelist: DB addr list: file locked, breaking lock
Now, I checked the docs, and apparently the setting for the
auto-whitelist location (auto_whitelist_path) was removed in 3.2.x and
I cannot for the life of me figure out how to tell my system where I
want it to place my awl.
That option wasn't removed from SA.. it was removed from the main conf
docs, as all of the AWL is now a plugin. That option is documented in
the docs for the AWL plugin, which is where it really belongs. (if the
option isn't valid without the plugin, then it in theory shouldn't be in
the main Conf manpage..)
See
http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Plugin_AWL.html
