I'm familiar with this implementation from SpamAssassin. I'm not seeing it's utility, however. How is it different from using TotalScore to filter messages? How is "maybe spam"/"spam" different from the Low/High Threshold settings?
What do you find lacking in the current options? Matti Haack wrote: > As I switched to single message scoring, it would be great to have the > spam score in a format that is easyly to filter in mail client. > Spamassasin uses besides the spam score an additional "graphical" spam > tag: > X-Spam-Level: ****** > > Assp could add a * for every 10 (or configurable) Spam-Score-Points > > X-Assp-Totalscore: 40 > X-ASSP-Spam-Level: **** > > I have many users who are afraid of missing a single message and who > don't like the idea that mail would be blocked on the server. > > So end users could filter their incomming spam in their clients (if > header contains "Spam-Level: **" move to "maybe spam" ; if > header contains "Spam-Level: ******" move to "spam"; if > header contains "Spam-Level: *********" delete from server) > > Matti > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
