You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/04/13 16:56:28 UTC
[Bug 3263] New: Expiry for SQL based AWL
http://bugzilla.spamassassin.org/show_bug.cgi?id=3263
Summary: Expiry for SQL based AWL
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P3
Component: spamassassin
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: dallase@nmgi.com
i have made a patch that allows sql-based AWL expiry to occur to prevent
unlimited growth of your sql-based AWL DB. the patch is mainly against sa-
learn because i didnt want to write a stand-alone app that only provided one
function.
the patch allows you to call sa-learn --awl-expire via a nighly cron to expire
entries that have not been touched for a while (default 30 days).
it provides a new conf option called auto_whitelist_expiry which takes the
number of seconds that you want to keep untouched entries in your AWL db.
Default is 2592000 which is 30 days.
it modifies the db schema in sql/awl_*.sql to include an indexed timestamp
field which is what expiration will work with.
it also updates the sql/README.awl docs with some info on expiration. And
thats about it.
i was thinking about putting the expiry code into SQLBasedAddrList.pm like
bayes does on the fly, but then i thought against it.... should expiry happen
on the fly for AWL?
d
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.