THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
For more information, please read the Mail::SpamAssassin::Conf documentation.
Possible autolearn states
In SpamAssassin 2.5 and 2.6, there were only three states for the autolearn result: ham, spam, and no.
- ham: the message was learned as ham (non-spam)
- spam: the message was learned as spam
- no: the message was not learned
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
- ham: the message was learned as ham (non-spam)
- spam: the message was learned as spam
- no: the specific message didn't achieve the proper threshold values
...
- and requirements to be learned
- disabled
...
- : the configuration specifies
bayes_auto_learn 0
oruse_bayes 0
and so no autolearning is attempted
...
- failed:
...
- autolearning was attempted, but couldn't complete. This happens if SpamAssassin can't gain a lock on the Bayes database files, etc.
- unavailable
...
- : autolearning not completed for any reason not covered above.
...
- It could be the message was already learned.