Oh yeah, I forgot to add implementation details:

The new DBBasedAddrList creates backward-compatible DB files.  It stores the
count of messages for a user as an int keyed by the email address (with some
characters converted to _), and the total accumulated score for the user is
a floating point number keyed by $addr.'|totscore', which should never clash
with an actual sender address (or in any case shouldn't break things too
badly).  So if you have a new DB file, the old code will still work against
it w/out any problems.  But then if you switch back to the new code again,
things will be miscalculated (since you'll have inc'd the count, without
changing the totscore).  If you have an old DB-file, then it'll basically
reset your AWL to count=0, score=0 -- but you're not really losing much
information, and there's no real way to guess what the totscore for existing
email addresses should be anyway.

The implementation of spamassassin -W/-R (ie add/remove addresses from AWL)
is to remove the address, or else to add the user with
count=1,totscore=-100.

I think that's about all that's relevant now...

C


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to