[SpamAssassin Wiki] Updated: AutolearningNotWorking

[sp...@incubator.apache.org]

   Date: 2004-07-13T14:55:00
   Editor: 66.92.69.213 <>
   Wiki: SpamAssassin Wiki
   Page: AutolearningNotWorking
   URL: http://wiki.apache.org/spamassassin/AutolearningNotWorking

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -6,8 +6,20 @@
 
 If a message has already been learned by SpamAssassin, then that message will not be learned again. Therefore, if you run a message through SpamAssassin to see why it was classified as spam or ham, and it has already been learned, you will always get the result "autolearn=no". (To see this more clearly, use the "-D" flag, and you will see debug output explaining that the message has already been learned.)
 
-    Furthermore, the score used to trigger autolearning is somewhat different than the one reported in the final score; therefore a score displayed in the headers that obstensibly should trigger autolearning will not do so. Again, use the "-D" flag to SpamAssassin, and you will see the score that is used to determine whether or not autolearning will be triggered.
+Furthermore, the score used to trigger autolearning is somewhat different than the one reported in the final score; therefore a score displayed in the headers that obstensibly should trigger autolearning will not do so. Again, use the "-D" flag to SpamAssassin, and you will see the score that is used to determine whether or not autolearning will be triggered.
 
 Finally, SpamAssassin requires at least 3 points from the header and 3 points from the body, to auto-learn as spam.  If either section contributes fewer points, the message will not be auto-learned.
 
 For more information, please read the Mail::SpamAssassin::Conf documentation.
+
+----
+
+In SpamAssassin 2.5 and 2.6, there were only three states for the autolearn result: ham, spam, and no.  In SpamAssassin 3.0, the result was enhanced to have six states: ham, spam, no, disabled, failed, and unavailable.
+
+''ham'' and ''spam'' are the same.  ''no'' is now explicitly that the message didn't achieve the proper threshold values.
+
+''disabled'' means that the configuration specifies {{{bayes_auto_learn 0}}} and so no autolearning is attempted.
+
+''failed'' means that autolearning was attempted, but couldn't complete.  This happens if SpamAssassin can't gain a lock on the Bayes database files, etc.
+
+''unavailable'' is now the catch-all for anything not covered above.