From: Nicolas KOWALSKI <Nicolas.Kowalski@imag.fr>
Subject: Re: nnimap subfolder problem
Date: Tue, 16 Oct 2001 16:01:56 +0200 [thread overview]
Message-ID: <vqo1yk3n0ob.fsf@olan.imag.fr> (raw)
In-Reply-To: <vafpu7nzoik.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 16 Oct 2001 15:46:11 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Right, but there is no generic connection between directories and the
>> delimiter character used in group names with IMAP.
>
> I vaguely recall that there is an IMAP protocol element where you can
> ask the server which character it uses as a hierarchy delimiter. Am I
> dreaming?
Mmh. I was wrong in my last post :
7.2.2. LIST Response
Contents: name attributes
hierarchy delimiter
name
The LIST response occurs as a result of a LIST command. It
returns a single name that matches the LIST specification. There
can be multiple LIST responses for a single LIST command.
<snip>
The hierarchy delimiter is a character used to delimit levels of
hierarchy in a mailbox name. A client can use it to create child
mailboxes, and to search higher or lower levels of naming
hierarchy. All children of a top-level hierarchy node MUST use
the same separator character. A NIL hierarchy delimiter means
that no hierarchy exists; the name is a "flat" name.
The name represents an unambiguous left-to-right hierarchy, and
MUST be valid for use as a reference in LIST and LSUB commands.
Unless \Noselect is indicated, the name MUST also be valid as an
argument for commands, such as SELECT, that accept mailbox
names.
Example: S: * LIST (\Noselect) "/" ~/Mail/foo
Nicolas.
next prev parent reply other threads:[~2001-10-16 14:01 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 [this message]
2001-10-16 18:12 ` Simon Josefsson
2001-10-17 4:27 ` Amos Gouaux
2001-10-16 13:59 ` Nicolas KOWALSKI
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=vqo1yk3n0ob.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).