We discovered recently that Dspam tokens were being stored in the database for too long (around 6 months) after having been moved to a new server, preventing Dspam from adjusting to new types of spam -- and training.
We have resolved this issue by reinstating token purging, which keeps the Dspam database lean and flexible. A consequence of this might have been that some users experience a less effective filter for a while, until their filter has adjusted again (each user has a separate token collection unique to their account).
Thereafter Dspam should be working optimally for everyone.
- Geir
|