GrayHat wrote: > Right; now, to create different "buckets" and have different "filtering > rules" one may add PopFile on the backend side (client) of the mail
> (possibly adding a spam probability header as well); at this point the > popfile will kick in allowing each mailbox owner to define his/her own > rules to categorize the emails; I think this may be a viable approach I think the tagging as spam and putting in a seperate (junk)folder is a flawed approach and only useful in a testing stage. Users can train assp by forwarding spam to a special address. That is very effective. I routinely open up an address which receives a lot of spam (games@, john@ etc.) then forward every spam email to assp and sooner or later almost all (but a few a week) spam dries up since assp learns how to filter them out. When you have a "tag as spam and junkfolder approach" you'll soon have a folder with 1000s of spam emails and a handful of legitimate emails. It's human nature to ignore this folder and check it less and less. The sender of the legitimate email thinks it arrived, since it didn't bounce, and becomes annoyed why you haven't replied yet. The best approach is to bounce spam, in that case the sender of a legitimate email will know it did not arrive and seek assistance or alternative ways to resend. Often resending an email slightly adjusted will be enough. And for those who insist, you can always add them to spamlover and have them figure it out from there. :-) Best regards, Jeroen ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
