From: Pawel Osiczko <posiczko@gmail.com>
To: info-gnus-english@gnu.org
Subject: nnimap-split-fancy across inbox boundaries?
Date: Sat, 25 Aug 2012 20:31:40 -0700 (PDT) [thread overview]
Message-ID: <acf0ec48-2fbb-4d14-b0da-dc8832d9bb1e@googlegroups.com> (raw)
Hello,
Having 2 IMAP inboxes defined, like so:
(setq gnus-select-method '(nnnil))
(setq gnus-secondary-select-methods
'(
(nnimap "0.foo"
(nnimap-address "imap.foo.com")
)
(nnimap "1.bar"
(nnimap-address "imap.bar.com")
)
)
)
I would love to apply the split rules across the inboxes, ie if an email from user@example.com arrives at 1.bar, I'd like to move it to 0.foo:some-group:
(setq nnimap-split-fancy
'(|
(: nnmail-split-fancy-with-parent)
(from "user@example.com"
"nnimap+0.foo:some-group" )
("INBOX")
)
)
(setq nnimap-split-methods 'nnimap-split-fancy)
The above splits to the group named nnimap+0.foo:some-group at 1.bar. Any hints how to make the split happen across the inbox boundaries to 0.foo:some-group?
Thank you,
Pawel
next reply other threads:[~2012-08-26 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 3:31 Pawel Osiczko [this message]
2012-08-27 1:46 ` Damon Haley
2012-09-05 14:12 ` Lars Ingebrigtsen
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=acf0ec48-2fbb-4d14-b0da-dc8832d9bb1e@googlegroups.com \
--to=posiczko@gmail.com \
--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).