Re: spam/ham autolearn (spamassassin) markings in summary

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 17 Dec 2003, wes@hardakers.net wrote:

> So, I just wanted to get spamassain working properly and to ensure
> that all the articles it "autolearned" as spam/ham truly were.  The
> problem is that you have to open the article to find out.  Well,
> I've now done this [...]

Cool.  I'll probably do something similar for the next release of
Gnus, as a real formatting specifier instead of a user format
function.  It will probably be two or three letter, one to indicate
the status and the rest to indicate the backend(s) used to detect
that it is spam/ham.

X-Spam-Status is not a reliably way to detect spamicity,
unfortunately.  Blacklists or blackholes, for instance, don't leave a
trace inside the message.  It's better to use the gnus-registry
tracking, which will automatically note when a message is tagged as
spam or ham, by spam/ham processing or incoming/autodetection mail
spam-splitting.  See the latest spam.el, I track the spam/ham
detection history of a message when I do autodetection in
spam-find-spam and spam-split for instance.

Ted