With a courier server, you get a response for the NAMESPACE
command as:
b NAMESPACE
* NAMESPACE (("INBOX." ".")) NIL (("shared." "."))
b OK NAMESPACE completed.
(The first set is for personal folders, second for other
users' - courier does not support this feature I guess, and
the third for shared folders. The second parameter is the
heirarchy delimiter).
This seems to say out of the gate that Courier only accepts INBOX. And
shared. As the heirarchy convention.. Which can only resolve client side
into having an INBOX -> Subdir -> Subdir tree instead of having a more
broad breakup.
I am trying to create a sibling of the INBOX and my clients are not able
to do this because of the above NAMESPACE convention.
Note that I cannot make head or tail out of this response to
the NAMESPACE
command: (uw-imapd)
b NAMESPACE
* NAMESPACE (("" "/")("#mhinbox" NIL)("#mh/" "/")) (("~"
"/")) (("#shared/" "/")("#ftp/" "/")("#news." ".")("#public/"
"/")) b OK NAMESPACE completed
Is it that it has multiple prefixes and heirarchy separators?
That's exactly what it looks like to me. UW can create as anything, an
inbox, a mailhome, a tilde, a shared folder, ftp, news, public.. I
wonder if Courier can be hacked to do it..
I like Courier for how it was to setup and what it does for me.. But
there are little bits of errata like this which just makes me, and I
know any client I hook up to this, flinch.
-a
10 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: Creating Fold...
