From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: imap splitting to mail.misc?
Date: Sun, 07 Jul 2013 11:54:01 +0800 [thread overview]
Message-ID: <87a9lz10va.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87txkdz1dp.fsf@enricoschumann.net>
Enrico Schumann <es@enricoschumann.net> writes:
> On Tue, 02 Jul 2013, Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>
> [...]
>
>>
>> And is it actually a mistake to leave anything in INBOX? Or rather, a
>> mistake to split things *back* into the INBOX? Maybe I should be making
>> myself a separate box and splitting all unmatched messages into that?
>> But I would still have to assume that some messages would end up in
>> "mail.misc", as they do now...
>>
>
> Hm, I don't use nnimap-split-fancy, but nnimap-split-rule. Then you
> don't need a 'catch-all' split rule. From the manual:
>
> "Nnmail users might recollect that the last regexp had to be empty to
> match all articles [...]. This is not required in nnimap. Articles
> not matching any of the regexps will not be moved out of your inbox."
>
> But that does not explain where "mail.misc" comes from....
>
> Regards,
> Enrico
With a little help off-list, I think I've figured it out. I've been
using bbdb/gnus-split-method, both with nnmail and nnimap. It appears
that, with nnimap, the value of bbdb/gnus-split-default-group comes into
play. That defaults to "mail.misc", and switching it to "INBOX" solved
the problem.
Why it was putting some messages into "mail.misc" and leaving others in
"INBOX" is a different mystery.
E
prev parent reply other threads:[~2013-07-07 3:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 8:21 Eric Abrahamsen
2013-07-02 10:45 ` Enrico Schumann
2013-07-03 4:58 ` Eric Abrahamsen
2013-07-03 10:24 ` Eric Abrahamsen
2013-07-07 3:54 ` Eric Abrahamsen [this message]
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=87a9lz10va.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).