Re: spam manual update for Gnus

["Miles Bader" <miles@gnu.org>]

On 4/21/06, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> Miles, applying the patch to Gnus trunk gives a lot of rejected
> hunks[1].  I'm not sure how we should proceed with this.  Ted?

I went through the conflicts, and most of them seemed fairly trivial
-- I guess minor changes in the Gnus trunk tripped up the patch, but
the text didn't seem to have changed greatly.  So I just forced them
to Chong's new text.

The exceptions are that two new (in the trunk, prior to merging
Chong's changes) menu entries, and one new info node (ibid) are now
missing; somebody should re-add them wherever is appropriate in
Chong's new structure:

These are the (now missing) menu entries:

* Spam ELisp Package Sorting and Score Display in Summary Buffer::
* SpamAssassin back end::

This is the (now missing) info node:


@node Spam ELisp Package Sorting and Score Display in Summary Buffer
@subsubsection Spam ELisp Package Sorting and Score Display in Summary Buffer
@cindex spam scoring
@cindex spam sorting
@cindex spam score summary buffer
@cindex spam sort summary buffer
@cindex spam

You can display the spam score of articles in your summary buffer, and
you can sort articles by their spam score.

First you need to decide which back end you will be using.  If you use
the @code{spam-use-spamassassin},
@code{spam-use-spamassassin-headers}, or @code{spam-use-regex-headers}
back end, the @code{X-Spam-Status} header will be used.  If you use
@code{spam-use-bogofilter}, the @code{X-Bogosity} header will be used.
If you use @code{spam-use-crm114}, any header that matches the CRM114
score format will be used.  As long as you set the appropriate back end
variable to t @emph{before} you load @file{spam.el}, you will be
fine.  @code{spam.el} will automatically add the right header to the
internal Gnus list of required headers.

To show the spam score in your summary buffer, add this line to your
@code{gnus.el} file (note @code{spam.el} does not do that by default
so it won't override any existing @code{S} formats you may have).

@lisp
(defalias 'gnus-user-format-function-S 'spam-user-format-function-S)
@end lisp

Now just set your summary line format to use @code{%uS}.  Here's an
example that formats the spam score in a 5-character field:

@lisp
(setq gnus-summary-line-format
 "%U%R %10&user-date; $%5uS %6k  %B %(%4L: %*%-25,25a%) %s \n")
@end lisp

Finally, to sort by spam status, either do it globally:

@lisp
(setq
 gnus-show-threads nil
 gnus-article-sort-functions
  '(spam-article-sort-by-spam-status))
@end lisp

or per group (@pxref{Sorting the Summary Buffer}).


-Miles
--
Do not taunt Happy Fun Ball.