How to determine unixhierarchysep *through* imap?

[Marc G. Fournier]

On Mon, 17 Apr 2006, David Lang wrote:

> from rfc 2501, a list will return this info
>
> a list "" ""
> * LIST (\Noselect) "." ""
> a OK Completed (0.000 secs 0 calls)

That should work:

. list "" ""
* LIST (\Noselect) "/" ""

Thanks ... will try and incorporate that ...

>
> David Lang
>
> On Mon, 17 Apr 2006, Marc G. Fournier wrote:
>
>> Date: Mon, 17 Apr 2006 21:54:11 -0300 (ADT)
>> From: Marc G. Fournier <scrappy at hub.org>
>> To: Cyrus Mailing List <info-cyrus at lists.andrew.cmu.edu>
>> Subject: How to determine unixhierarchysep *through* imap?
>> 
>> 
>> How are other admin interfaces determining whether its '.' or '/'?  I'm 
>> using PHP, and checked  ". capability" based on one persons suggestion, but 
>> it just returns:
>> 
>> ===
>> * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE 
>> UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT 
>> THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE AUTH=DIGEST-MD5 
>> AUTH=CRAM-MD5 SASL-IR LISTEXT LIST-SUBSCRIBED X-NETSCAPE
>> ===
>> 
>> could be that I'm missing something in there that is the 'switch', but I've 
>> run the above with unixhierarchysep set to 1 and 0, and the output looks 
>> identical ...
>> 
>> Right now, my interface is doing a simple:
>>
>>      /* Attempting to create a new mailbox. */
>>      $newmailbox = 
>> "{".$mail_server_name.":".$mail_server_port."}user.".$account_name;
>>      $sent_mail_folder = $newmailbox.".sent-mail";
>>
>>      if(imap_createmailbox($mbox,imap_utf7_encode($newmailbox))) {
>>        if(imap_createmailbox($mbox,imap_utf7_encode($sent_mail_folder))) {
>> 
>> But, of course, with unixhierarchysep set to 1, it has to be 
>> user/$account_name ...
>> 
>> Help? :)
>> 
>> 
>> ----
>> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
>> Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664
>> ----
>> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
>> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
>> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>> 
>
> -- 
> There are two ways of constructing a software design. One way is to make it 
> so simple that there are obviously no deficiencies. And the other way is to 
> make it so complicated that there are no obvious deficiencies.
> -- C.A.R. Hoare
>
>
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664