MBOX-Line: From mrc at CAC.Washington.EDU  Thu Aug  3 11:17:10 2006
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc@CAC.Washington.EDU>
Date: Fri Jun  8 12:34:37 2018
Subject: [Imap-protocol] IMAP/Pine List query
In-Reply-To: <GLVU3AykpxJLiEjGrlFisg.md5@libertango.oryx.com>
References: <089601c6b713$60732ba0$8710e0c3@ftgate.lan> 
	<Pine.OSX.4.64.0608030959370.408@pangtzu.panda.com>
	<GLVU3AykpxJLiEjGrlFisg.md5@libertango.oryx.com>
Message-ID: <Pine.OSX.4.64.0608031111040.408@pangtzu.panda.com>

On Thu, 3 Aug 2006, Arnt Gulbrandsen wrote:
> Mark Crispin writes:
>> Are you saying that your mail store does not have INBOX?  /inbox is not 
>> equivalent to INBOX.
> On cyrus, user.arnt is equivalent to INBOX. On uw, /var/spool/mail/arnt is 
> equivalent to INBOX.

No, they are not equivalent.  These are names which may access the same 
data in certain configurations of certain implementations, but they are 
not INBOX.  INBOX has a special meaning in IMAP.

[Incidentally, /var/spool/mail/mrc does not access my INBOX on any 
installation of UW imapd that I use.]

> The only thing I can see about /inbox that's different 
> from those two is that it contains 'inbox' as a level of hierarchy, but is 
> that forbidden?

/inbox is simply an ordinary name.  It is not INBOX, even if it happens to 
access the same data in a particular configuration on Richard's server.

You also missed the point of my comment; I asked Richard if his mail store 
did not have INBOX.  I asked because he said that he felt that no untagged 
LIST results should be returned for "tag LIST INBOX %", yet his hierarchy 
had /inbox which suggested that there was, indeed, a mailbox that has the 
role of INBOX in his server.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

