Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Spam.el tutorial
Date: Tue, 16 Dec 2003 21:16:44 +0000	[thread overview]
Message-ID: <877k0wh39f.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <87brq8h3g0.fsf@emptyhost.emptydomain.de>

Kai Grossjohann <kai@emptydomain.de> writes:

> From a short look at your post it seems that you give spam-autodetect
> a list of things to try, then it will do so.  My problem, then, is
> that I don't know what to put into that list.

Oops.  Completely off-base it seems.

I think *now* I understand: spam-autodetect can do like spam-split,
but without splitting.

It doesn't handle spam reporting at all, IIUC.  Silly me, I only
thought about spam reporting, not about spam detection ;-)

For me, spam splitting is done on the server side with bogofilter, and
there is no easy way for me to tell Gnus to invoke bogofilter on the
server side.  So spam-autodetect is out, I guess.

(I'd need a local bogofilter database it seems.  Wonder whether it's
worth it.  Maybe NOCEM can help?  What does it do, anyway?  There is a
vague connection between NOCEM and spam in my mind.)

Kai




  reply	other threads:[~2003-12-16 21:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14  2:25 Xavier Maillard
2003-12-14  3:40 ` Ted Zlatanov
2003-12-14 12:28 ` Reiner Steib
2003-12-14 22:38   ` Xavier Maillard
2003-12-16 19:10 ` Kai Grossjohann
2003-12-16 20:57   ` Ted Zlatanov
2003-12-16 21:12     ` Kai Grossjohann
2003-12-16 21:16       ` Kai Grossjohann [this message]
2003-12-16 22:16         ` Ted Zlatanov
2003-12-17  5:29           ` Xavier Maillard
2003-12-17 16:49             ` Ted Zlatanov
2003-12-17 22:26               ` Xavier Maillard
2003-12-18 16:35                 ` Ted Zlatanov
2003-12-19 10:38                   ` Xavier Maillard
2003-12-17  5:33   ` Xavier Maillard

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=877k0wh39f.fsf@emptyhost.emptydomain.de \
    --to=kai@emptydomain.de \
    /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).