From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: planned spam.el features
Date: Mon, 27 Jan 2003 13:20:13 -0500 [thread overview]
Message-ID: <4nbs22a202.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87lm19q7bb.fsf@pobox.com> (Stephen Zander's message of "Sat, 25 Jan 2003 12:54:16 -0800")
On Sat, 25 Jan 2003, gibreel@pobox.com wrote:
>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
> Ted> OK, now that spam.el is somewhat stable, I'm going to start
> Ted> working on the next bunch of features:
>
> A simple request (unless it's already in the latest version). I use
> fetchmail & mailagent to retrieve & split mail from various lists
> into seperate files before reading it with Gnus. I now also run
> bogofilter against all email prior to handing it to mailagent for
> splitting. While I have spam-use-bogofilter set to t, this means
> that bogofilter gets invoked with the wrong command line switches,
> '-n' & '-s' instead of '-S' and '-N', because bogofilter has already
> added the message to its database.
>
> If I write a small patch to allow for this alternative, would you be
> willing to add it? Also, does anyone have a prefered name for the
> variable that enables such switching?
Sure, I'll take a look. Maybe spam-bogofilter-force-reclassify?
The upcoming spam.el changes will track messages as they are processed
as ham or spam. You will be able to force spam.el to recognize that a
message has already been processed as spam/ham by a certain backend
spam/ham processor, so force-reclassify will not be needed. These
changes won't happen soon, though, so your patch would be literally a
patch in the meanwhile :)
Ted
next prev parent reply other threads:[~2003-01-27 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 19:22 Ted Zlatanov
2003-01-24 20:01 ` Kai Großjohann
2003-01-24 20:25 ` Ted Zlatanov
2003-01-25 20:54 ` Stephen Zander
2003-01-27 18:20 ` Ted Zlatanov [this message]
2003-02-22 7:00 ` Stephen Zander
2003-02-24 15:42 ` 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=4nbs22a202.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).