From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around
Date: Mon, 11 Jan 2016 14:56:42 +0800 [thread overview]
Message-ID: <87mvsceh91.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87vb73qe84.fsf@tullinup.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> Eric writes:
>
> [...trim your quotes, folks...]
>
>> (setq nnimap-split-fancy
>> '(|
>> ("From" "googlealerts.*" "INBOX.google-alerts")
>> (any "c[...]" "INBOX.tmp")
>> ;; Invoke the BBDB
>> (: (lambda ()
>> (car (bbdb/gnus-split-method))))
>> ;; Default mailbox
>> ("INBOX" "")))
>>
>> I'm not a splitting expert (I've stopped using it, and wasn't very good
>> at it to begin with), but there are a couple of things odd about this.
>> First, I don't think that's how you're supposed to use
>> `bbdb/gnus-split-method'. The comments in bbdb-gnus indicate that you're
>> supposed to do something like this:
>>
>> (setq nnmail-split-methods 'bbdb/gnus-split-method)
>> (setq bbdb/gnus-split-nomatch-function nnimap-split-fancy)
>
> You don't have to, I have been using the former way since days of yore.
>
> The point is that I want the rules before the call to bbdb/gnus-split-
> method to "overrule" bbdb.
>
> (E.g. I want commit messages to go to a commit-group, regardless of
> whether I have the person who did the commit configured in bbdb to be
> split into another group).
>
> I have, however, also these two bbdb-splitting related settings:
>
> (setq bbdb/gnus-split-default-group nil
> bbdb/gnus-split-nomatch-function nil)
>
> I don't know if the first could be of relevance here - I guess not,
> because then Gijs' emails would have been going to mail.misc...
>
> (IMAP is complicated.)
Right, but the basic point remains that bbdb/gnus-split-method will
hijack the whole process unless you stop it -- though there are multiple
ways of stopping it. Anyhow, Gijs should have a few options to play with
now...
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2016-01-11 6:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 11:04 Gijs Hillenius
2016-01-05 11:17 ` Eric Abrahamsen
2016-01-05 11:26 ` CHENG Gao
2016-01-05 12:38 ` Gijs Hillenius
2016-01-05 12:54 ` Eric Abrahamsen
[not found] ` <mailman.1737.1451998456.843.info-gnus-english@gnu.org>
2016-01-05 13:07 ` Gijs Hillenius
2016-01-05 13:24 ` Eric Abrahamsen
[not found] ` <mailman.1740.1452000295.843.info-gnus-english@gnu.org>
2016-01-05 14:16 ` Gijs Hillenius
2016-01-05 14:48 ` Gijs Hillenius
2016-01-05 15:11 ` Eric Abrahamsen
[not found] ` <mailman.1745.1452006719.843.info-gnus-english@gnu.org>
2016-01-07 7:28 ` Gijs Hillenius
2016-01-07 8:54 ` Eric Abrahamsen
[not found] ` <mailman.1877.1452156877.843.info-gnus-english@gnu.org>
2016-01-07 9:14 ` Gijs Hillenius
2016-01-07 14:03 ` Eric Abrahamsen
[not found] ` <mailman.1882.1452175419.843.info-gnus-english@gnu.org>
2016-01-08 7:54 ` is this a bug in gnus v5.13? " Gijs Hillenius
2016-01-08 10:33 ` Eric Abrahamsen
[not found] ` <mailman.1947.1452249217.843.info-gnus-english@gnu.org>
2016-01-08 11:27 ` Gijs Hillenius
2016-01-09 4:02 ` Eric Abrahamsen
2016-01-09 9:44 ` Adam Sjøgren
2016-01-11 6:56 ` Eric Abrahamsen [this message]
2016-01-11 9:28 ` Adam Sjøgren
[not found] ` <mailman.2029.1452332680.843.info-gnus-english@gnu.org>
2016-01-11 9:29 ` Gijs Hillenius
2016-01-11 9:33 ` Adam Sjøgren
2016-01-11 9:40 ` Eric Abrahamsen
[not found] ` <mailman.2130.1452505220.843.info-gnus-english@gnu.org>
2016-01-11 11:34 ` Gijs Hillenius
2016-01-11 11:48 ` Adam Sjøgren
[not found] ` <mailman.2136.1452512951.843.info-gnus-english@gnu.org>
2016-01-11 12:54 ` Gijs Hillenius
2016-01-11 13:18 ` Gijs Hillenius
2016-01-11 15:47 ` Adam Sjøgren
[not found] ` <mailman.2152.1452527287.843.info-gnus-english@gnu.org>
2016-01-18 8:08 ` FIXED " Gijs Hillenius
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=87mvsceh91.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).