From: "Steven E. Harris" <steven.harris@tenzing.com>
Subject: nnimap RFC2342 support (IMAP4 Namespace)
Date: 31 Jan 2001 13:33:29 -0800 [thread overview]
Message-ID: <87puh3flue.fsf@torus.tenzing.com> (raw)
When I've had to move folders around on different IMAP servers, I've
run into problems with nnimap's treatment of folder
names. Specifically, nnimap requires the user to specify the folder
name *as it's implemented* on the IMAP server, rather than as a more
abstract path. As an example, where I once had
nnimap+speakeasy:mailing-lists/gnus-ding
my ISP changed servers and I had to manually move that to
nnimap+speakeasy:INBOX.mailing-lists.gnus-ding
while MS Outlook just figured out the change without trouble. (Sorry
to hold Outlook up in a positive light.)
Today I stumbled upon RFC2342¹ - IMAP4 Namespace - that looks like it
addresses this exact problem. Has anyone taken a look at this to see
how hard it would be to add support to nnimap?
Footnotes:
¹ http://www.rfc-editor.org/rfc/rfc2342.txt
--
Steven E. Harris :: steven.harris@tenzing.com
Tenzing :: http://www.tenzing.com
next reply other threads:[~2001-01-31 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 21:33 Steven E. Harris [this message]
2001-01-31 22:21 ` Simon Josefsson
2001-02-01 2:34 ` NAGY Andras
2001-02-01 3:06 ` NAGY Andras
2001-02-01 18:37 ` Steven E. Harris
2001-02-11 1:58 ` NAGY Andras
2001-02-01 19:29 ` Steven E. Harris
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=87puh3flue.fsf@torus.tenzing.com \
--to=steven.harris@tenzing.com \
/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).