From: Bruce Stephens <bruce+usenet@cenderis.demon.co.uk>
Subject: Re: bug in spam.el and expiry issue
Date: Fri, 24 Jan 2003 11:15:09 +0000 [thread overview]
Message-ID: <871y327q9u.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: <m3u1fzkva4.fsf@heechee.beld.net>
Ted Zlatanov <tzz@lifelogs.com> writes:
[...]
> With the following group parameters:
>
> ((total-expire . t)
> (spam-contents gnus-group-spam-classification-ham)
> (spam-process
> (gnus-group-ham-exit-processor-whitelist))
> (expiry-wait . immediate)
> (expiry-target . "temporarygroup"))
>
> I get ham-marked articles processed into the whitelist at summary
> exit, before they are moved to "temporarygroup". This is the expected
> correct behavior.
I get the expected behaviour now. Probably I just messed up, and was
still using the version where the bogofilter ham setting was
predicated on ifile. Anyway, it works now, which is wonderful.
(Thanks for pointing out expiry-target, BTW. I didn't know that
functionality existed.)
prev parent reply other threads:[~2003-01-24 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 17:46 Bruce Stephens
2003-01-21 17:07 ` Ted Zlatanov
2003-01-22 15:02 ` Bruce Stephens
2003-01-24 4:48 ` Ted Zlatanov
2003-01-24 11:15 ` Bruce Stephens [this message]
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=871y327q9u.fsf@cenderis.demon.co.uk \
--to=bruce+usenet@cenderis.demon.co.uk \
/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).