From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ifile-discuss <ifile-discuss@yahoogroups.com>, ding <ding@gnus.org>
Subject: Re: ifile-gnus.el version 0.3.5 (spam-filtering / general email classification)
Date: Sun, 13 Oct 2002 07:47:45 -0400 [thread overview]
Message-ID: <m38z128sri.fsf@heechee.beld.net> (raw)
In-Reply-To: <uv61y6yroa4.fsf@suspiria.ai.mit.edu> (jhbrown@ai.mit.edu's message of "10 Oct 2002 17:12:51 -0400")
On 10 Oct 2002, jhbrown@ai.mit.edu wrote:
> You can use ifile-gnus either as a spamfilter, or to automatically
> and adaptively classify all of your incoming email. My personal
> experience has been that ifile is 80-90% accurate in general email
> classification, and insanely accurate in spam vs. non-spam
> classification.
I set up a first cut of the ifile functionality for spam.el; like the
other checks, you just set spam-check-ifile to t and the
ifile-spam-filter function will be invoked with nil as the non-spam
group name parameter, so it will return either spam-split-group or
nil. I wrap the call to ifile-spam-filter in a
let ((ifile-primary-spam-group spam-split-group)) so ifile will use
the spam-split-group name.
Let me know if there are problems.
Some ideas: it would be nice if ifile-gnus.el could support nnimap,
and if it could hook at group exit time, to look at articles marked as
spam. spam.el already does that:
(add-hook 'gnus-summary-prepare-hook 'spam-summary-prepare)
(add-hook 'gnus-summary-prepare-exit-hook 'spam-summary-prepare-exit)
where spam-summary-prepare marks unread articles in
spam-junk-mailgroups with the spam-mark, and spam-summary-prepare-exit
invokes the bogofilter registration currently on all articles marked
as spam, whether manually or through spam-summary-prepare. I think
ifile could be added to spam-summary-prepare-exit if there's interest.
That would add some precision to the already good ifile spam
detection, by classifying messages marked as spam even if they are not
moved to a spam group.
Thanks
Ted
next parent reply other threads:[~2002-10-13 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uv61y6yroa4.fsf@suspiria.ai.mit.edu>
2002-10-13 11:47 ` Ted Zlatanov [this message]
[not found] ` <uv6ptuecjxd.fsf@suspiria.ai.mit.edu>
2002-10-15 16:22 ` Ted Zlatanov
2004-10-03 0:26 ` ifile-gnus.el now unsupported Jeremy Brown
2004-10-04 16:57 ` 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=m38z128sri.fsf@heechee.beld.net \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=ifile-discuss@yahoogroups.com \
/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).