Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Z Maze <dmaze@mit.edu>
Subject: Re: Bogofilter
Date: Mon, 27 Jan 2003 14:01:02 -0500	[thread overview]
Message-ID: <y6865saquxd.fsf@multics.mit.edu> (raw)
In-Reply-To: <m2r8ayh7zm.fsf_-_@bluesteel.grierwhite.com>

chris@grierwhite.com (Christopher J. White) writes:
> I'm intrigued...my spam load has reached critical levels, so I'm
> interested in trying out some spam filtering techniques.  Are you
> using bogofilter with gnus?  If so, what's your experience, does it
> ever filter out "good" email as spam (as it's statistical in nature)?
> If you don't have several hundred spam messages around to train it,
> how else do you train it, or do I have to wait til I get enough saved
> up spam?

I use ifile, not bogofilter, but the two packages seem to be similar
in nature.  Yes, I get some false positives with ifile.  It's also not
like I didn't have a big pile of spam sitting around before I started
using ifile (I hand-sorted it into its own group); if nothing else,
you can set up a Hotmail account and wait for a couple of weeks.  :-)

> Finally, how do you integrate bogofilter with gnus for mail reading
> (read via POP3, stored as nnml).

You're using

> User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (powerpc-apple-darwin)

so you can just use the functions in spam.el.  My .gnus file has

(setq
      gnus-spam-newsgroup-contents
      '(("nnml:mail.misc.spam" gnus-group-spam-classification-spam)
	("nnml:.*" gnus-group-spam-classification-ham))
      gnus-spam-process-newsgroups
      '(("nnml:.*" (gnus-group-spam-exit-processor-ifile
		    gnus-group-ham-exit-processor-ifile)))
      gnus-spam-process-destinations
      '(("nnml:.*" "nnml:mail.misc.spam"))
      spam-junk-mailgroups '("mail.misc.spam")
      spam-split-group "mail.misc.spam"
      spam-use-ifile t
)

and I call (: spam-split) in nnmail-split-fancy.  I think all of these
should Just Work for you if you change group names appropriately and
substitute bogofilter for ifile.

-- 
David Maze             dmaze@mit.edu          http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
	-- Abra Mitchell


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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874r7vclji.fsf@ibook.optushome.com.au>
     [not found] ` <844r7vjc3l.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]   ` <81k7gq1z6a.fsf@shasta.cs.uiuc.edu>
     [not found]     ` <m2r8ayh7zm.fsf_-_@bluesteel.grierwhite.com>
2003-01-27 19:01       ` David Z Maze [this message]
     [not found]         ` <9cfvg09rx37.fsf@rogue.ncsl.nist.gov>
2003-01-29  7:10           ` Bogofilter Kai Großjohann
2003-01-29 19:59             ` Bogofilter Ian Soboroff
     [not found]               ` <4nlm12ehn5.fsf@lockgroove.bwh.harvard.edu>
2003-01-30 18:09                 ` Bogofilter Kai Großjohann
2003-01-31 16:46                   ` Bogofilter Ted Zlatanov
     [not found] ` <87ptqiodvb.fsf@unix.home>
2003-01-29 11:06   ` spam assassin filtering Alain Picard
2003-01-29 15:35     ` Michael Below
     [not found]       ` <87u1fr7lwn.fsf@jan.korger>
2003-01-29 21:14         ` Vasily Korytov
2003-01-29 21:52           ` Tim Haynes

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=y6865saquxd.fsf@multics.mit.edu \
    --to=dmaze@mit.edu \
    /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).