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

[Wes Hardaker <wes@hardakers.net>]

>>>>> On Thu, 18 Dec 2003 11:41:29 -0500, Ted Zlatanov <tzz@lifelogs.com> said:

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

I know there is already a format spec that marks spam with $ I think, right?

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

I apply spamassassin during processing of incoming mail.  I also don't
split inside gnus, and split directly into imap folders via procmail
(that way when I occasionally have to use other mail readers, I don't
have 3000 messages in my inbox because only gnus knows how to split
it).

In short, the example is a bit tailored to my environment (which is
why I said it was an "example" and didn't submit a patch ;-)
-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett