From: "Saša Janiška" <gour@atmarama.com>
To: ding@gnus.org
Subject: Re: Immediate ham processing
Date: Wed, 05 Apr 2017 10:53:46 +0200 [thread overview]
Message-ID: <87zifvz145.fsf@atmarama.com> (raw)
In-Reply-To: <87wpbivdur.fsf@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
Teemu Likonen <tlikonen@iki.fi> writes:
> My gnus-bogofilter package has functions bogofilter-register-ham (and
> -spam) which you may find useful. I use package instead of Gnus's own
> spam package.
Could it be that your package has problem when one uses Gnus registry?
Now I have the following setup (with multiple IMAP accounts):
(setq gnus-secondary-select-methods
'(
(nnimap "gour"
(nnimap-address "mail.server.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)
("List-Id" ".*<swisseph.yahoogroups.com" "lists.sweph")
(: bogofilter-split "spam" "unsure" "INBOX")
nil)))
but I still occasionally - not always, see that messages are split into
'bogus' mail group?
Sincerely,
Gour
--
One who sees inaction in action, and action in inaction,
is intelligent among men, and he is in the transcendental position,
although engaged in all sorts of activities.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-04-05 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 10:54 Julien Cubizolles
2017-03-21 15:39 ` Teemu Likonen
2017-04-04 16:50 ` Julien Cubizolles
2017-04-06 14:31 ` Saša Janiška
2017-04-05 8:53 ` Saša Janiška [this message]
2017-08-03 19:58 ` 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=87zifvz145.fsf@atmarama.com \
--to=gour@atmarama.com \
--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).