Mercury Suggestions
spamhalter feature request: "analog" SPAM level header

Properly learned Spamhalter is very bipolar due used technology. Nearly all classifications have 0% or 100% result. Other results are only marginal or extreme cases.

Spamhalter is designed to decide if message is spam or not. It cannot produce result like 'it is maybe spam'. So, it have just one level - if classification is higher - message is spam. This configured level is essencial for corrections and training functions, becasue corrections and learning process working with this level value.

So, do not filter spam by your spam probability level. Allways use leve configured in Spamhalter. If classification is higher, then Spamhalter add "Spam detected" additional header what is designed for filtering purpose.

By this level Spamhalter knows itself, if message is spam or not, and this information is used for self-learning. If message is corrected, then this level is used for check, if correction is sucessfull or not.

If you are adding your individual levels by percentage instead of "spam detected" headers, then all of this cannot work properly. Please, use only configured spam level. Spamhalter is really sure if message is spam or not. There is not place for 'maybe'. And if human found error, then made correction immediately.
 

<p>Properly learned Spamhalter is very bipolar due used technology. Nearly all classifications have 0% or 100% result. Other results are only marginal or extreme cases.</p><p>Spamhalter is designed to decide if message is spam or not. It cannot produce result like 'it is maybe spam'. So, it have just one level - if classification is higher - message is spam. This configured level is essencial for corrections and training functions, becasue corrections and learning process working with this level value.</p><p>So, do not filter spam by your spam probability level. Allways use leve configured in Spamhalter. If classification is higher, then Spamhalter add "Spam detected" additional header what is designed for filtering purpose.</p><p>By this level Spamhalter knows itself, if message is spam or not, and this information is used for self-learning. If message is corrected, then this level is used for check, if correction is sucessfull or not.</p><p>If you are adding your individual levels by percentage instead of "spam detected" headers, then all of this cannot work properly. Please, use only configured spam level. Spamhalter is really sure if message is spam or not. There is not place for 'maybe'. And if human found error, then made correction immediately.  </p>

Hi,

SpamAssassin has the feature to add a header containing the SPAM probability in stars like "X-SPAM-Level: ******" .
The huge use I made from it is that every user can set up (or adapt) his individual SPAM filter at client level (PMail, Outlook, Firebird...) by filtering messages for that header.

Whereas it is complicated to filter for "X-SPAMWALL: probability" > 60 % (you had to set up at least 9 rules filtering for
"X-SPAMWALL: probability - 6." --> pass on
"X-SPAMWALL: probability - 6"  --> delete
"X-SPAMWALL: probability - 7." --> pass on
"X-SPAMWALL: probability - 7"  --> delete
"X-SPAMWALL: probability - 8" --> pass on
"X-SPAMWALL: probability - 8."  --> delete
"X-SPAMWALL: probability - 9" --> pass on
"X-SPAMWALL: probability - 9."  --> delete
"X-SPAMWALL: probability - 100.")  --> delete
it is easy to delete all messages containing the Header "X-SPAM-Level: ******" AND (setting up a 2nd rule) move all messages containing "X-SPAM-Level: ****" (i.e. 40 to 60%) to a SPAM-folder.

This is especially useful in an ISP environment where it is tricky (or forbidden!) to delete messages for clients. Every client gets the tagged messages and filters in his own reponsibility instead of blaming us for "wrong" filtering.

 

Would it be possible to add such a feature? I suggested just to set 1 star for every 10 percent.

 

Thank you, Rainer

[edit]adjusted tags[/edit]

<P>Hi,</P> <P>SpamAssassin has the feature to add a header containing the SPAM probability in stars like "X-SPAM-Level: ******" . The huge use I made from it is that every user can set up (or adapt) his individual SPAM filter at client level (PMail, Outlook, Firebird...) by filtering messages for that header.</P> <P>Whereas it is complicated to filter for "X-SPAMWALL: probability" > <STRONG>60 %</STRONG> (you had to set up at least 9 rules filtering for "X-SPAMWALL: probability - 6." --> pass on "X-SPAMWALL: probability - 6"  --> <EM>delete</EM> "X-SPAMWALL: probability - 7." --> pass on "X-SPAMWALL: probability - 7"  --> <EM>delete</EM> "X-SPAMWALL: probability - 8" --> pass on "X-SPAMWALL: probability - 8."  --> <EM>delete</EM> "X-SPAMWALL: probability - 9" --> pass on "X-SPAMWALL: probability - 9."  --> <EM>delete</EM> "X-SPAMWALL: probability - 100.")  --> delete it is easy to delete all messages containing the Header "X-SPAM-Level: <STRONG>******</STRONG>" AND (setting up a 2nd rule) move all messages containing "X-SPAM-Level: ****" (i.e. 40 to 60%) to a SPAM-folder.</P> <P>This is especially useful in an ISP environment where it is tricky (or forbidden!) to delete messages for clients. Every client gets the tagged messages and filters in his own reponsibility instead of blaming us for "wrong" filtering.</P> <P mce_keep="true"> </P> <P>Would it be possible to add such a feature? I suggested just to set 1 star for every 10 percent.</P> <P mce_keep="true"> </P> <P>Thank you, Rainer</P> <P>[edit]adjusted tags[/edit]</P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft