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
>
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
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 betwe
"Kevin J. Menard, Jr." wrote:
>
> Hey Ken,
>
> Thursday, June 21, 2001, 11:51:11 AM, you wrote:
>
> KM> Unless any new bugs or issues are found with this release, this will be
> KM> the code which will be merged into the main Cyrus tree and appear in one
> KM> of the next two standard release
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 imapd.conf
Hey Ken,
Thursday, June 21, 2001, 11:51:11 AM, you wrote:
KM> Unless any new bugs or issues are found with this release, this will be
KM> the code which will be merged into the main Cyrus tree and appear in one
KM> of the next two standard releases (2.0.15 or 2.0.16).
How will this be merged?
