Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: "Saša Janiška" <gour@atmarama.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Is there a simple way to set up spam filtering?
Date: Sat, 30 Jan 2016 21:16:47 +0200	[thread overview]
Message-ID: <87egcydgio.fsf@iki.fi> (raw)
In-Reply-To: <1454178890.2637.62.camel@atmarama.com> (=?utf-8?Q?=22Sa?= =?utf-8?Q?=C5=A1a_Jani=C5=A1ka=22's?= message of "Sat, 30 Jan 2016 19:34:50 +0100")


[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]

Saša Janiška [2016-01-30 19:34:50+01] wrote:

> So, I'be very thankful if you can provide some help how to either use
> Gnus' spam package or your gnus-bogofilter package?

Here's a configuration example for my gnus-bogofilter.el. You can add
this code in your Gnus init file (gnus.el):

    ;; Load gnus-bogofilter.el package.
    (require 'gnus-bogofilter)

    (setq nnmail-split-methods 'nnmail-split-fancy
          nnmail-mail-splitting-decodes t
          nnmail-split-fancy
          '(| (: bogofilter-split "spam" "unsure")
              ;; You can add split rules here if you want to.
              "misc"))

You should also read the docs for nnmail-split-fancy variable so that
you understand how mail splitting works. The above configuration will
move detected incoming spam messages to group "spam", unsure messages to
group "unsure" and all good (ham) messages to group "misc".

In Gnus summary buffer you can use commands M-x bogofilter-register-spam
and M-x bogofilter-register-ham to train Bogofilter's database. Those
will register the current message (or all marked messages) for
Bogofilter. Command M-x bogofilter-check will display current message's
status and spam score. Also see the functions' documentation.

And that's pretty much it.

-- 
/// Teemu Likonen   - .-..   <https://github.com/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]



  reply	other threads:[~2016-01-30 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03  7:44 Sivaram Neelakantan
2016-01-03 18:04 ` Teemu Likonen
2016-01-30 18:34   ` Saša Janiška
2016-01-30 19:16     ` Teemu Likonen [this message]
2016-01-30 20:23       ` Saša Janiška
2016-01-30 21:00         ` Teemu Likonen
2017-04-03  7:39           ` Saša Janiška
     [not found] <mailman.1601.1451839085.843.info-gnus-english@gnu.org>
2016-01-03 16:49 ` notbob

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=87egcydgio.fsf@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=gour@atmarama.com \
    --cc=info-gnus-english@gnu.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).