Hi,
Think of the reference name as being the connected directory.
For the following examples, think about a UNIX filesystem for the
namespace.
If you do
tag LIST foo
then you'll see foo in your home directory. If you do
tag list mail/ foo
then you'll see foo in your mail/
A reference name of is not the same as a reference name of . Also,
to avoid possible ambiguity, it is better that non-empty reference names
terminate with the hierarchy delimiter, e.g.
tag LIST Specials\\ Read
rather than
tag LIST Specials Read
Consider the following command:
tag LIST
At 2004-06-02 13:15:18 +0200, [EMAIL PROTECTED] wrote:
I've never seen that I can create an directory in the meaning of
reference with an Client.
I think you're confused: the reference name is simply an argument that
tells LIST which results to return.
For example, consider a hypothetical
I've never seen that I can create an directory in the meaning of
reference with an Client.
I think you're confused: the reference name is simply an argument that
tells LIST which results to return.
For example, consider a hypothetical server with this mailbox hierarchy:
/users/a/INBOX
As an aside, I disapprove of the practices of mailboxes under INBOX and
Trash mailboxes.
IMAP does not prohibit either of these practices, but these practices
are associated with
substantial client and user confusion.
Mark, would you expand on this a little, please? I am currently looking at
At 2004-06-02 16:25:07 +0200, [EMAIL PROTECTED] wrote:
So If I'm connected with user a, I will always have the current
directory /users/a and the incoming client Reference Name will
always be
The client can send whatever reference name it wants.
OK, let me try to explain this differently.
