From: Russ Allbery <rra@stanford.edu>
Subject: No Gnus doesn't like the obsolete spam syntax
Date: Tue, 09 Aug 2005 19:53:20 -0700 [thread overview]
Message-ID: <874q9yy02n.fsf@windlord.stanford.edu> (raw)
Just a quick note in case it saves someone else some time.
I used to have:
(custom-set-variables
'(gnus-parameters
'(("^nnml:spam\\..*"
(spam-contents gnus-group-spam-classification-spam)
(spam-process (gnus-group-spam-exit-processor-bogofilter
gnus-group-ham-exit-processor-bogofilter))))))
(with more gnus-parameters, but that's the relevant ones). This no longer
works with No Gnus (version in the headers). I'm not entirely sure why,
but following the manual's instructions and then fiddling a little to
figure out what they really mean, the following *does* work:
(custom-set-variables
'(gnus-parameters
'(("^nnml:spam\\..*"
(spam-contents gnus-group-spam-classification-spam)
(spam-process ((spam spam-use-bogofilter)
(ham spam-use-bogofilter)))))))
It took me a little bit to get the syntax right, since for some reason I
read the manual suggestion and thought it said to replace
gnus-group-spam-exit-processor-bogofilter
with
('(spam spam-use-bogofilter))
literally. That just silently fails with no error message, apparently due
to having one too many layers of parens.
(Yes, I know you can do this all inside customize. I hate the interface
for customize and also prefer to have commented configurations so that I
can remember why I changed something, which means that I do a lot of
writing code based directly on the manual or using customize to generate a
first draft and then tweaking it.)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next reply other threads:[~2005-08-10 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 2:53 Russ Allbery [this message]
2005-09-20 16:13 ` Ted Zlatanov
2005-09-20 17:26 ` Russ Allbery
2005-09-21 14:28 ` 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=874q9yy02n.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).