Nuno Silva wrote:
As noted by Ken Murchison a while back the alternative namespace does
not change the spool structure (files and folders on disk) to provide
the alternative namespace, therefor there is *one* drawback:
You can't create subfolders of INBOX. while using the alternate
At 05:15 AM 23/6/2001, Ken Murchison wrote:
The bottom line: if you simply install this code and change nothing,
then it will run the same as your current setup.
For more info, read doc/overview.html, and imapd.conf(5).
The docs are good and should be read.
I however do see a problem between
As noted by Ken Murchison a while back the alternative namespace does
not change the spool structure (files and folders on disk) to provide
the alternative namespace, therefor there is *one* drawback:
You can't create subfolders of INBOX. while using the alternate
namespace (these folders are
Ken Murchison wrote this a few weeks ago in this list:
[snip...]
Configuring the server to use the alternate namespace is done by setting
altnamespace: yes in imapd.conf. The prefixes for the shared
namespace and other users' namespace can be set as well. The relevant
options from
I just made the third and final beta of the alternate namespace code
available at:
ftp://ftp.oceana.com/pub/cyrus-imapd-2.0.14-NAMESPACE-r3.tar.gz
http://www.oceana.com/ftp/cyrus-imapd-2.0.14-NAMESPACE-r3.tar.gz
You can also grab it via anonymous CVS at CMU by checking out the
alt-namespace
