Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam filtering using IMAP ?
Date: Thu, 09 Jan 2003 14:38:17 -0500	[thread overview]
Message-ID: <4n4r8im7va.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <uadiaqgf0.fsf@castify.net> (Arnd Kohrs's message of "Thu, 09 Jan 2003 20:20:03 +0100")

On Thu, 09 Jan 2003, kohrs@castify.net wrote:
> Can one spam filter when using nnimap for all email?
> 
> I guess the answer is still "NO!".
> 
> IMHO the reason for this is that when nnimap splits, it only loads
> the headers and not the bodies of the articles, so that the spam
> recognition which is based on the bodies may not be used.

As far as spam.el is concerned, it only looks at whatever is in the
current buffer when spam-split is invoked.  Spam and ham processors
use the full body of the message at summary exit, so in spam-split we
have the only difference of opinion between the nnimap and other
backends.

It's worth noting that 

1) many people don't use spam.el (the majority)

2) we don't want nnimap to download full articles when splitting, even
   with spam.el, because whitelist/blacklist/BBDB/blackhole splitters
   don't need the full article

So I would suggest that this could be an option that spam-split could
set when dealing with a nnimap backend and a splitter that needs the
full message.  For instance, spam-use-ifile would require full nnimap
downloads, but spam-use-blackholes wouldn't.

nnimap gurus, is that possible?

Ted



  reply	other threads:[~2003-01-09 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09 19:20 Arnd Kohrs
2003-01-09 19:38 ` Ted Zlatanov [this message]
2003-01-10  2:02   ` Simon Josefsson
2003-01-16  7:20 ` Mats Lidell
2003-01-16  9:40   ` Ted Zlatanov
2003-01-16 10:43     ` Mats Lidell
2003-01-16 11:22       ` Ted Zlatanov
2003-01-16 12:41         ` Mats Lidell
2003-01-16 14:11           ` Ted Zlatanov
2003-01-16 15:32 ` Kai Großjohann
2003-01-16 20:02   ` Mats Lidell

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=4n4r8im7va.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).