From: "Saša Janiška" <gour@atmarama.com>
To: info-gnus-english@gnu.org
Subject: Re: Is there a simple way to set up spam filtering?
Date: Mon, 03 Apr 2017 09:39:17 +0200 [thread overview]
Message-ID: <87a87ylz2y.fsf@atmarama.com> (raw)
In-Reply-To: <8760yadbp3.fsf@iki.fi>
[-- Attachment #1.1: Type: text/plain, Size: 2856 bytes --]
Teemu Likonen <tlikonen@iki.fi> writes:
> It sounds like you are using IMAP method. Then you need to read the info
> page "(gnus) Client-Side IMAP Splitting" and use nnimap-split-fancy
> variable.
After long time and some experience with spam package I decided to
replace it with (simpler) gnus-bogofilter. Spam package worked OK, but
was not able to properly handly false positives…
> After reading the info page "(gnus) Fancy Mail Splitting" I'd say that
> putting the symbol nil as the split rule will leave the message where it
> was. Here's again my fancy split rule example:
>
> (| (: bogofilter-split "spam" "unsure")
> ;; You can add split rules here if you want to.
> "misc"))
>
> So in the example replace the string "misc" with symbol nil. I haven't
> tested it and I don't use IMAP splitting so I give no guarantees.
I use several IMAP accounts and my setup looks as:
(setq gnus-secondary-select-methods
'(
(nnimap "gour"
(nnimap-address "…“")
(nnimap-server-port 993)
(nnimap-stream ssl)
(nnimap-authinfo-file "~/.authinfo.gpg")
(nnimap-inbox ("INBOX" "spam"))
(nnimap-split-methods 'nnimap-split-fancy)
(nnimap-split-fancy
(|
(: gnus-registry-split-fancy-with-parent)
(: bogofilter-split "spam" "unsure")
("List-Id" ".*<swisseph.yahoogroups.com" "lists.sweph")
("List-Id" ".*udruga\-lista\.atmarama\.org" "lists.udruga")
nil)))
(nnimap "anotherid"
(nnimap-address "imap.gmail.com")
(nnimap-server-port 993)
(nnimap-stream ssl)
(nnimap-authinfo-file "~/.authinfo.gpg")
(nnimap-inbox ("INBOX"))
(nnimap-split-methods 'nnimap-split-fancy)
(nnimap-split-fancy
(|
(: gnus-registry-split-fancy-with-parent)
(: bogofilter-split "spam" "unsure")
nil)))
...
but, after launching Gnus, it puts new messages into 'bogus' groups and
i see the following in Messages buffer:
Error in ‘nnmail-split-methods’; using ‘bogus’ mail group:
(void-function bogofilter-split)
I was trying to replace 'nil' with "INBOX" which was used with 'spam'
package, but cannot get rid of bogus groups. Any hint what might be
wrong?
Sincerely,
Gour
--
Just try to learn the truth by approaching a spiritual master.
Inquire from him submissively and render service unto him.
The self-realized souls can impart knowledge unto you because
they have seen the truth.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-04-03 7:39 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
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 [this message]
[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=87a87ylz2y.fsf@atmarama.com \
--to=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).