Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Spam.el tutorial
Date: Wed, 17 Dec 2003 06:33:59 +0100	[thread overview]
Message-ID: <plop874qw0qa7s.fsf@gnu-rox.org> (raw)
In-Reply-To: <87pteok281.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Tue, 16 Dec 2003 19:10:54 +0000")

Kai Grossjohann <kai@emptydomain.de> disait récemment que :

> I like the idea about a tutorial.  Instead of contributing my own
> setup (which tries to do the same as Reiner's but probably fails), I'd
> like to suggest some scenarios.

That is ok for me ;) (Note I didn't contributed by giving my own setup
which is quite "funny" at that time)

> * A user who wants to rely only on Emacs, with no external software,
>   and doesn't trust statistics.
>
>   I guess this means blacklists and whitelists, mostly.  Maybe BBDB
>   comes in, too.  Maybe spam senders are blacklisted whereas ham
>   senders are whitelisted.  Not sure how BBDB comes in.  Maybe
>   somebody does it.
>
> * Like above but with statistics.
>
>   So that means to use spam-stat.el.  Does it make a difference
>   whether one uses nnimap or another backend?
>
>   Incoming spam is put into the nnchoke:spam group.  Not sure whether
>   it is useful to do spam training on those articles, suggest a setup.
>
>   False negatives and false positives are sent to spam-stat.el; not
>   sure whether they should go through nnchoke:makespam and
>   nnchoke:makeham groups or not.  Suggestions?
>
> * Like previous but use an external program for the statistics.  Still
>   do it all through Gnus.
>
> * Like previous, but filter incoming mail through the external program
>   before Gnus sees it.  (==> spam-use-foo-headers)

Good idea. I more or less was thinking of organizing the "maybe future
tutorial" this way with "scenarios". I also guess there are quite a few
more we can elaborate on but my guess is, only users can tell what is
their own situation and how they setup things accordingly to their
specific organization.

> Kai

zeDek
-- 
 In Gruuik we trust




      parent reply	other threads:[~2003-12-17  5:33 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
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 [this message]

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=plop874qw0qa7s.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.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).