[Tickets #1152] NEW: Tag level help text confusion

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1152
-----------------------------------------------------------------------
 Ticket     | 1152
 Created By | josh at endries.org
 Summary    | Tag level help text confusion
 Queue      | Sam
 Version    | HEAD
 State      | New
 Priority   | 1. Low
 Type       | Enhancement
 Owners     | 
-----------------------------------------------------------------------


josh at endries.org (2005-01-13 14:06) wrote:

Hello,

Some of my users have been confused by the descriptions for tag levels in
SAM. After listening to their confusion and explaining what the levels mean,
I'm submitting this simple patch to change the text to Hit Level (the only
one we use):

--- help.xml    Sun Jun 27 22:07:12 2004
+++ help2.xml   Thu Jan 13 17:02:27 2005
@@ -22,15 +22,17 @@
     <title>General Options: Hit Level</title>
     <heading>Hit Level</heading>
     <para>
-        Specify the minimum score required to add a <b>X-SPAM: Yes</b>
+        Specify the minimum score required to add a <b>X-Spam-Flag:
YES</b>
         header for messages identified as SPAM. This header can be used
for
         filtering rule creation.
     </para>
     <para>
-        The lower the score, the more aggressive tagging becomes. For
example,
-        a score of 2.0 will add the header to messages of 2.0 and above,
and
-        is a very aggressive setting. This setting should generally be
equal
-        to or lower than the <i>Tag Level</i> setting (if enabled).
+       The lower the Hit Level, the more aggressive the filter will be
when
+       marking messages as spam. For example, a Hit Level of 2.0 will mark
+       any message with a score of 2.0 and higher as spam. This is a very
+       aggressive setting. The Hit Level should generally be higher than
the
+       <i>Tag Level</i> setting (if enabled). A Hit Level of 5.0 is the
+       default setting.
     </para>
 </entry>