Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: imap splitting to mail.misc?
Date: Tue, 02 Jul 2013 16:21:42 +0800	[thread overview]
Message-ID: <87y59pl6cp.fsf@ericabrahamsen.net> (raw)

I'm still working through the transition to imap...

One thing about imap splitting is confusing me: many messages are
getting split to a "mail.misc" group, when I have no such group in any
of my split methods. Apparently it's a default split target, but
messages seem to be going there semi-randomly for different accounts.
For some accounts, *all* of the messages that aren't split-matched end
up there, for others only some. All account servers have something like
this:

(nnimap-inbox "INBOX")
(nnimap-split-methods bbdb/gnus-split-method))

and then later in .gnus.el:

(setq bbdb/gnus-split-nomatch-function 'nnimap-split-fancy)

And:

(setq nnimap-split-fancy `(|
                           ; many splits 
			   "INBOX"))

I've also tried removing bbdb/gnus-split-method and setting it to
nnimap-split-fancy directly, with the same results.

I assume "mail.misc" is some sort of universal default, but with the
above settings no mail should end up there, should it?

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...

Thanks,
Eric




             reply	other threads:[~2013-07-02  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02  8:21 Eric Abrahamsen [this message]
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

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=87y59pl6cp.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).