From: Kai Grossjohann <kgrossjo@eu.uu.net>
Subject: Re: IMAP Splitting with multiple mailboxes
Date: Tue, 18 May 2004 18:14:05 +0200 [thread overview]
Message-ID: <86oeol7lwy.fsf@rumba.de.uu.net> (raw)
In-Reply-To: <20040518115804.A30128@gwyn.tux.org>
Timothy Brown <tim@tux.org> writes:
> I have three nnimap select methods selecting from different servers.
> When using nnimap splitting - fancy splitting - where do the messages
> end up if there is no declaration of nnimap+host:folder,
I think that splitting cannot cross server boundaries. That is, if
you specify "INBOX.foo" as the target group for a server, then it
will be on the server currently being split.
> and just a folder declaration? Do they end up local to the nnimap
> server that is being split from at the time?
I think so.
> Can splitting occur between servers?
I think that's not possible.
> Can I see messages on one server and have them moved via nnimap to a
> different server using splitting?
Well, splitting happens before you see the messages. So you can't
see them before splitting... Maybe you mean something else?
> How does : spam-split interact with nnimap fancy splitting,
> particularly in the concept of having multiple virtual servers?
Huh. Dunno. I guess that if it says that INBOX.spam is the target,
then this will be on the server being split...
A question you didn't ask is how to have different split rules for
different servers. The variable nnimap-split-rule appears to allow
this, but I don't see how it would work for fancy splitting.
[time passes]
Oh! Now I see. Here's what you do:
(setq nnimap-split-rule '(("server1" ("INBOX" tim-split-fancy-1))
("server2" ("INBOX" tim-split-fancy-2))))
(setq tim-split-fancy-rule-1
-value-that-looks-like-nnimap-split-fancy-)
(setq tim-split-fancy-rule-2
-another-value-looking-like-nnimap-split-fancy-)
(defun tim-split-fancy-1 ()
(let ((nnimap-split-fancy tim-split-fancy-rule-1))
(nnimap-split-fancy)))
(defun tim-split-fancy-2 ()
(let ((nnimap-split-fancy tim-split-fancy-rule-2))
(nnimap-split-fancy)))
The idea is that you define two different functions to perform the
splitting, and both functions essentially do like the function
nnimap-split-fancy, but temporarily change the value of the
nnimap-split-fancy variable.
That's a common Lisp trick.
All of the above is untested. I never tried anything that fancy with
splitting ;-)
Kai
next prev parent reply other threads:[~2004-05-18 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 21:50 Spam splitting and multiple nnimap methods Timothy Brown
2004-05-18 9:53 ` Jonas Steverud
2004-05-18 12:53 ` Timothy Brown
2004-05-18 13:50 ` Jonas Steverud
2004-05-18 14:02 ` IMAP Splitting with multiple mailboxes (was Re: Spam splitting and multiple nnimap methods) Timothy Brown
2004-05-18 14:13 ` IMAP Splitting with multiple mailboxes Kai Grossjohann
2004-05-18 14:15 ` Timothy Brown
2004-05-18 15:53 ` Kai Grossjohann
2004-05-18 15:58 ` Timothy Brown
2004-05-18 16:14 ` Kai Grossjohann [this message]
2004-05-18 14:13 ` Spam splitting and multiple nnimap methods Jonas Steverud
2004-05-18 19:11 ` Ted Zlatanov
2004-05-18 22:19 ` Timothy Brown
2004-05-19 11:36 ` Jonas Steverud
2004-05-19 14:50 ` Ted Zlatanov
2004-05-19 14:48 ` Ted Zlatanov
2004-05-20 10:27 ` Yair Friedman
2004-05-20 18:49 ` Ted Zlatanov
2004-05-22 23:45 ` Lars Magne 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=86oeol7lwy.fsf@rumba.de.uu.net \
--to=kgrossjo@eu.uu.net \
/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).