Fritz Borgstedt wrote:
I think that 3 would make the most sense and be the easiest of the 3
to write, but they would still all be tough to implement.
It is not necessary to move files between the directories after the
first rebuild.
The email-interface is quite capable of adjusting the spamdb and the
error-folders are a quite nice longtime-memory.
fritz
But that's exactly the point. I'd like a safeguard against the longterm
memory of the errors folder. If a client mis-classifies an email, it
will stay in that folder forever, skewing the bayesian db. Additionally,
say a non-whitelisted server that that sends ham has an innocent PTR/RBL
error, their ham mail will go into the spam collection. It would take a
long time for that mail to be recycled out, and for that time, the db
will be poisoned.
It would just be good to have an easier way to manage these collections,
to protect against misclassification and poisoning.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
