all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to split (IMAP client side split) incoming mails into groups for multiple emails addresses with Gnus
Date: Tue, 09 Jan 2018 00:20:22 +0100	[thread overview]
Message-ID: <86wp0sq6o9.fsf@zoho.com> (raw)
In-Reply-To: mailman.7044.1515449313.27995.help-gnu-emacs@gnu.org

gnuforever wrote:

> How should I do the split for my 2
> imap accounts?

Are you currently getting them into the same
group - from your example, the one
called INBOX?

And you have two additional groups,
INBOX.folder1 and INBOX.folder2, but they don't
get populated?

If so, you must correct the rules for
`nnmail-split-methods' prior to the INBOX case
(which always will be true because "" applies
to everything, which is the only rule that
works in the above scenario).

You have

    "from:.*friends@domain.com"

But examine the article (mail/post) which has
gone into INBOX but you expected/wanted it to
go to INBOX.folder1. Look at the From header of
that mail in particular. Does it really match
your rule for INBOX.folder1?

Also, hit `B q' in article mode to test where
it will go. If it says INBOX and not
INBOX.folder1, it means your expression doesn't
match and the only one that does is the
universal "", which puts it in INBOX.

PS. Also consider finding more descriptive
    names than folder1 and folder2.

-- 
underground experts united
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2018-01-08 23:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6956.1515312486.27995.help-gnu-emacs@gnu.org>
2018-01-07 21:01 ` How to split (IMAP client side split) incoming mails into groups for multiple emails addresses with Gnus Emanuel Berg
2018-01-08 22:08   ` gnuforever
     [not found]   ` <mailman.7044.1515449313.27995.help-gnu-emacs@gnu.org>
2018-01-08 23:20     ` Emanuel Berg [this message]
2018-01-10 23:02       ` gnuforever
2018-01-11 12:36         ` Alberto Luaces
     [not found]         ` <mailman.7197.1515674209.27995.help-gnu-emacs@gnu.org>
2018-01-11 18:32           ` Emanuel Berg
     [not found]       ` <mailman.7178.1515625372.27995.help-gnu-emacs@gnu.org>
2018-01-10 23:42         ` Emanuel Berg
2018-01-14 21:05           ` gnuforever
     [not found]           ` <mailman.7391.1515963940.27995.help-gnu-emacs@gnu.org>
2018-01-15  0:18             ` Emanuel Berg
2018-01-15  5:35               ` gnuforever
     [not found]               ` <mailman.7409.1515994562.27995.help-gnu-emacs@gnu.org>
2018-01-15  7:38                 ` Emanuel Berg
2018-01-16 19:44                   ` gnuforever
     [not found]                   ` <mailman.7478.1516131886.27995.help-gnu-emacs@gnu.org>
2018-01-17  2:13                     ` Emanuel Berg
2018-01-17  9:45                       ` gnuforever
2018-01-07  8:07 gnuforever
2018-01-09  8:42 ` Alberto Luaces

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=86wp0sq6o9.fsf@zoho.com \
    --to=moasen@zoho.com \
    --cc=help-gnu-emacs@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.