From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Need help with spam stuff.
Date: Tue, 15 Jul 2003 23:40:05 +0200 [thread overview]
Message-ID: <plop87smp7cvuy.fsf@gnu-rox.org> (raw)
In-Reply-To: <4nhe5n4lur.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Tue, 15 Jul 2003 15:43:24 -0400")
[-- Attachment #1: Type: text/plain, Size: 3784 bytes --]
On 15 jui 2003, Ted Zlatanov told this:
On Tue, 15 Jul 2003, zedek@gnu-rox.org wrote:
> > I am trying to write a small document onto the french Gnus user
> > site [1] about configuring Gnus to fight spam using Ted's work.
> >
> > As I am not a real expert at this, I would expect your help ;)
>
> Feel free to ask questions, I'll answer as best I can.
I was almost sure you would answer to that thread :) \o/
> > What are according to your current settings the proper way to
> > configure Gnus for that ? What's the best approach to get, to have
> > it working perfectly ? What spam filter to use and how ?
>
> spam.el tries to avoid these decisions. I have seen users who want
> everything automatic, other users want only incoming mail splitting,
> others want only marked spam/ham transfer at summary exit time. Each
> user seems to like something different for a spam filter, too (since
> you can combine filters, the total number of possibilities is very
> large).
This won't help to document the basis of the setting then ;)
> In terms of "most popular" spam filter, SpamAssassin and Bogofilter
> seem to be very popular. Both are supported by spam.el, one by
> spam-use-regex-headers (which is configured for SpamAssassin by
Is this related to the spamassassin header tags ?
[...]
> > I have my own ideas on the subject as I have configured mine, but I
> > need more feedbacks from other people to be as accurate as
> > possible. What did people use : hand writing or customize stuff ?
> > Why one way and not the other ?
>
> The manual section about spam.el gives very few ELisp examples for
> these two reasons: one, it's hard to give an example when people
> almost certainly will want something different from everyone else for
> filtering spam; two, Customize is much better as a common
> customization interface. Group and topic parameters are the other
> configuration piece, and that's pretty simple as well if done through
> the proper interface in Gnus (`G c').
Agree with that even if I am one of this hand-writtend maniac :) The
more I advance in writing the howto, the harder it is for me to take
the good decision. Spam is something more difficult I have imagined.
>
> I recommend Customize all the way, it's much harder to get it wrong.
Sure but as I am totally n00b at this I won't recommend that or at
least won't give bad explanation on that. I have never used any
Customize things until now so ... :)
> I had at least one person say they prefer hand-written customization,
You now have 2 :)
> and that's fine with me as long as I don't get bug reports because
> users misconfigured things.
Agree.
> My personal spam-related settings as of now:
>
> (setq spam-use-bbdb t spam-use-regex-headers t ; does X-Spam-Flag by
> default spam-use-blackholes (stringp (executable-find "dig"))
> spam-blackhole-good-server-regex "134.174" ;; my local subnet
> gnus-spam-newsgroup-contents '(("spam"
> gnus-group-spam-classification-spam)) spam-mark-only-unseen-as-spam t
> ;; split incoming mail according to the following rules.
> nnmail-split-methods 'nnmail-split-fancy nnmail-split-fancy '(| (:
> gnus-registry-split-fancy-with-parent)
>
> ;; check SpamAssassin early
> (: spam-split 'spam-use-regex-headers)
>
> ;; many irrelevant intermediate rules omitted
>
> (: spam-split)
>
> ;; default mailbox
> "mail"))
Wow I may have missed some options. /me needs to read the documentation
one more time.
> Ted
zeDek
--
http://www.gnusfr.org -- French Gnus user site
Anti-war disclaimer:
"Bombing for peace is like fucking for virginity"
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-07-15 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 18:06 Xavier Maillard
2003-07-15 19:43 ` Ted Zlatanov
2003-07-15 21:40 ` Xavier Maillard [this message]
2003-07-21 15:28 ` Ted Zlatanov
2003-07-18 6:19 ` Xavier Maillard
2003-07-21 15:34 ` 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=plop87smp7cvuy.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
--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).