From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: bug in spam.el and expiry issue
Date: Tue, 21 Jan 2003 12:07:54 -0500 [thread overview]
Message-ID: <4n7kcy2zyt.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <873cnqqrjj.fsf@cenderis.demon.co.uk> (Bruce Stephens's message of "Sat, 18 Jan 2003 17:46:56 +0000")
On Sat, 18 Jan 2003, bruce+usenet@cenderis.demon.co.uk wrote:
> First the typo:
Thanks, fixed.
> Secondly, how do I sanely use spam.el with auto-expire (or
> total-expire)? It seems that spam gets categorised OK, but the ham
> never gets processed, since (presumably) by the time the check
> happens, it's marked with E, which is correctly not processed.
Ham will only get processed in ham groups, are you sure you are in a
ham group and have a ham processor defined? The processing should
happen before the expired-mark is applied, but I have not tested that
particular setup, so if you could check and let me know, I'd
appreciate it. I may have to modify the behavior of total and auto
expiry a little when spam.el hooks into the summary exit, if the
expiry happens before spam-summary-prepare-exit is invoked.
Ted
next prev parent reply other threads:[~2003-01-21 17:07 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 [this message]
2003-01-22 15:02 ` Bruce Stephens
2003-01-24 4:48 ` Ted Zlatanov
2003-01-24 11:15 ` Bruce Stephens
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=4n7kcy2zyt.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).