From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: Trouble with spam.el and ifile
Date: Wed, 08 Jan 2003 11:15:18 -0500 [thread overview]
Message-ID: <y68k7hf39ex.fsf@multics.mit.edu> (raw)
In-Reply-To: <y68n0mb39sn.fsf@multics.mit.edu> (David Z Maze's message of "Wed, 08 Jan 2003 11:07:04 -0500")
David Z Maze <dmaze@MIT.EDU> writes:
> *enlightenment* I want to set
>
> (setq gnus-spam-newsgroup-contents
> '(("nnml:.*" gnus-group-spam-classification-ham)
> ("nnml:mail.misc.spam" gnus-group-spam-classification-spam)))
>
> since it looks like the magic in gnus-define-group-parameter picks the
> last matching regexp from the alist.
Replacing experimentation with enlightenment, this is backwards; it
takes the *first* regexp. So I now have in my .gnus:
(setq gnus-spam-newsgroup-contents
'(("nnml:mail.misc.spam" gnus-group-spam-classification-spam)
("nnml:.*" gnus-group-spam-classification-ham))
gnus-spam-process-newsgroups
'(("nnml:.*" (gnus-group-spam-exit-processor-ifile)))
gnus-spam-process-destinations
'(("nnml:.*" "nnml:mail.misc.spam"))
spam-junk-mailgroups '("mail.misc.spam")
spam-split-group "mail.misc.spam"
spam-use-ifile t)
And it appears to do almost everything I want, except for sorting away
spam or ham appearing in the other sort of group.
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next prev parent reply other threads:[~2003-01-08 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 16:52 David Z Maze
2003-01-07 19:47 ` Ted Zlatanov
2003-01-07 21:05 ` David Z Maze
2003-01-07 22:07 ` Ted Zlatanov
2003-01-07 22:32 ` David Z Maze
2003-01-07 22:42 ` David Z Maze
2003-01-08 4:55 ` Ted Zlatanov
2003-01-08 15:11 ` Ted Zlatanov
2003-01-08 16:07 ` David Z Maze
2003-01-08 16:15 ` David Z Maze [this message]
2003-01-08 16:25 ` Ted Zlatanov
2003-01-08 16:18 ` 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=y68k7hf39ex.fsf@multics.mit.edu \
--to=dmaze@mit.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).