From: Nicolas KOWALSKI <Nicolas.Kowalski@imag.fr>
Subject: Re: nnimap subfolder problem
Date: Tue, 16 Oct 2001 15:59:00 +0200 [thread overview]
Message-ID: <vqo669fn0t7.fsf@olan.imag.fr> (raw)
In-Reply-To: <ilu4roz1zje.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Tue, 16 Oct 2001 15:32:05 +0200")
Simon Josefsson <jas@extundo.com> writes:
>
> But if you used the Cyrus IMAPD server, all your users would be
> creating mailboxes containing `.' for hierarchies instead. :-)
>
Argh... :-).
> My point is, the hierarchy delimiter is not agreed on, and with IMAP
> it may even change between each hierarchy (you could e.g. have a
> mailbox called foo.bar/baz#boo&apa and each of the characters could be
> "real" hierarchy delimiters).
No no. The RFC says :
5.1.1. Mailbox Hierarchy Naming
If it is desired to export hierarchical mailbox names, mailbox names
MUST be left-to-right hierarchical using a single character to
separate levels of hierarchy. The same hierarchy separator character
is used for all levels of hierarchy within a single name.
> I'm not sure how this could be implemented, suggestions welcome.
I also searched the RFC for something like "what's your delimiter ?",
but it does not seem to be supported. Sigh.
I will look forward.
Thanks for your answers.
Nicolas.
next prev parent reply other threads:[~2001-10-16 13:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 11:13 Nicolas KOWALSKI
2001-10-16 11:41 ` Simon Josefsson
2001-10-16 12:02 ` Nicolas KOWALSKI
2001-10-16 12:35 ` Simon Josefsson
2001-10-16 13:04 ` Nicolas KOWALSKI
2001-10-16 13:32 ` Simon Josefsson
2001-10-16 13:46 ` Kai Großjohann
2001-10-16 14:01 ` Nicolas KOWALSKI
2001-10-16 18:12 ` Simon Josefsson
2001-10-17 4:27 ` Amos Gouaux
2001-10-16 13:59 ` Nicolas KOWALSKI [this message]
2001-10-16 18:27 ` Steinar Bang
2001-12-04 23:48 Kevin Hilman
2001-12-07 14:26 ` Simon Josefsson
2001-12-07 17:23 ` Kevin Hilman
2001-12-07 19:29 ` Simon Josefsson
2001-12-10 19:48 ` Kevin Hilman
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=vqo669fn0t7.fsf@olan.imag.fr \
--to=nicolas.kowalski@imag.fr \
/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).