From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: sorting summary on spamassassin score
Date: Thu, 22 Apr 2004 14:30:13 -0400 [thread overview]
Message-ID: <4nwu47j26i.fsf@lifelogs.com> (raw)
In-Reply-To: <87n055nnjg.fsf@uwo.ca> (Dan Christensen's message of "Wed, 21 Apr 2004 15:22:59 -0400")
On Wed, 21 Apr 2004, jdc@uwo.ca wrote:
> Wes and Adam, thanks for the suggestions.
I'm not sure who to thank, but I added the code you have below to
spam.el for general use. Right now only SpamAssassin is supported,
but it's intended for any backend that can score on a header. If I
can get a consensus on who came up with ideas and implementation, I'll
put that in the ChangeLog.
The main difference is that in my version, any spam headers, not just
X-Spam-Status, are supported.
So, how does it work? You just use spam-initialize as usual.
The only three things users will need to do:
1)
(defalias 'gnus-user-format-function-S 'spam-user-format-function-S)
if they want to use %uS in the summary line format. I'm considering
making this a built-in, e.g. %$ but I'm not sure yet.
2) set spam-use-spamassassin, spam-use-spamassassin-headers, or
spam-use-regex-headers BEFORE they run spam-initialize.
Conveniently, this can now be done like so:
(spam-initialize 'spam-use-spamassassin ...)
which will set spam-use-spamassassin to t BEFORE any intialization is
done. Very useful, and you don't need (setq spam-use-spamassassin t)
before spam-initialize anymore.
3) in the groups of interest, set the group article sorting to use
spam-article-sort-by-spam-status, that is, set
gnus-article-sort-functions to
'(spam-article-sort-by-spam-status). You may need
gnus-show-threads set to nil.
next prev parent reply other threads:[~2004-04-22 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 18:59 Dan Christensen
2004-04-07 19:05 ` Wes Hardaker
2004-04-07 23:33 ` Adam Sjøgren
2004-04-21 19:22 ` Dan Christensen
2004-04-22 18:30 ` Ted Zlatanov [this message]
2004-04-23 13:53 ` Dan Christensen
2004-04-23 14:05 ` Adam Sjøgren
2004-04-27 22:41 ` Ted Zlatanov
2004-04-27 23:05 ` Wes Hardaker
2004-04-27 23:09 ` Michael Shields
2004-05-20 18:45 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nwu47j26i.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).