From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: Splitting across backends...
Date: 22 Apr 1999 18:09:14 +0200 [thread overview]
Message-ID: <ilu676ok579.fsf@xiphias.pdc.kth.se> (raw)
In-Reply-To: wmperry@aventail.com's message of "21 Apr 1999 13:00:53 -0500"
wmperry@aventail.com (William M. Perry) writes:
> Is it possible yet to do mail splitting to a backend _other_ than the one
> doing the retrieval?
>
> I currently keep all of my email on my laptop, but would prefer to leave
> the vast majority of it in IMAP back in seattle. Email things that I tend
> to deal with on long plane rides (Emacs/W3, XEmacs, etc), I want to have
> local to the laptop so I can do things unplugged.
>
> So I want to have the imap splitting code split some things into a nnml
> folders, and the rest into just normal imap folders.
This isn't possible. Currently all backends need to do their own
splitting (it just happens to be that all mail backends except nnimap
uses the same splitting code -- no, nnimap can't share that code).
Backend independent splitting would be cool.
-s
prev parent reply other threads:[~1999-04-22 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-21 18:00 William M. Perry
1999-04-21 23:15 ` Wes Hardaker
1999-04-22 15:07 ` Kai.Grossjohann
1999-04-22 16:18 ` Simon Josefsson
1999-04-23 22:47 ` Wes Hardaker
1999-04-22 16:09 ` Simon Josefsson [this message]
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=ilu676ok579.fsf@xiphias.pdc.kth.se \
--to=jas@pdc.kth.se \
--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).