Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: info-gnus-english@gnu.org
Subject: Mail-splitting confusion
Date: Wed, 14 Oct 2015 17:44:37 +0300	[thread overview]
Message-ID: <87k2qpldbe.fsf@mithlond.arda> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]

I'm confused about Gnus's mail-splitting back-ends. How does Gnus decide
which back-end to use?

For example, I have different select methods, including things like
this:

    (setq gnus-select-method '(nnnil "")
          gnus-secondary-select-methods
          '((nnml ""
                  (nnml-directory "~/Mail")
                  (nnml-active-file "~/Mail/active"))
            (nnml "other"
                  (nnml-directory "~/other")
                  (nnml-active-file "~/other/active"))))

Then I have some split rules:

    (setq nnmail-split-methods 'nnmail-split-fancy
          nnmail-split-fancy
          '(|
            ;; Various rules here and the final destination:
            "misc"))

So incoming mail goes normally to "misc" group which is ~/Mail/misc
directory in the file system. But how does Gnus decide to put under
~/Mail and not under ~/other (see my other nnml configuration above)? Is
it possible to put (split) some mail to "nnml:foo" and some to
"nnml+other:bar"?

It seems that none of the examples in Gnus manual tell how to change the
destination back-end or how to split different mail to different
back-ends.

PS. And my terminology may also be wrong. I'm not always sure when to
speak of back-ends, select methods or servers.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]



             reply	other threads:[~2015-10-14 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:44 Teemu Likonen [this message]
2015-10-14 19:20 ` Teemu Likonen

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=87k2qpldbe.fsf@mithlond.arda \
    --to=tlikonen@iki.fi \
    --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).