At 12:48 AM 04/10/2002 -0700, [EMAIL PROTECTED] wrote:
>On Wed, 2002-04-10 at 07:59, [EMAIL PROTECTED] wrote:
> >> Anthony Brock schrieb am Tue, Apr 09, 2002 at 11:19:28PM -0700:
> >> > Where would you find this patch?
> >>
> >> Mmmh, maybe my post was a littly fast - I was sure I saw it flying
>
On Wed, 2002-04-10 at 07:59, [EMAIL PROTECTED] wrote:
> Anthony Brock schrieb am Tue, Apr 09, 2002 at 11:19:28PM -0700:
> > Where would you find this patch?
>
> Mmmh, maybe my post was a littly fast - I was sure I saw it flying around
> somewhere. However, you may begin with
>
> http://www.s
Anthony Brock schrieb am Tue, Apr 09, 2002 at 11:19:28PM -0700:
> Where would you find this patch?
Mmmh, maybe my post was a littly fast - I was sure I saw it flying around
somewhere. However, you may begin with
http://www.surf.org.uk/downloads/HIERSEP-r2.patch
but that seems to apply to 2.
Where would you find this patch?
Tony
At 11:00 PM 04/09/2002 -0700, you wrote:
>Russell schrieb am Mon, Apr 08, 2002 at 05:29:56PM +0100:
> >> Ok, after much hunting finally discovered its not implemented in
> >2.0.16. Ooops.
>
>There exists a patch to have it in 2.0.16.
>
>
>
>Birger
*
Russell schrieb am Mon, Apr 08, 2002 at 05:29:56PM +0100:
> Ok, after much hunting finally discovered its not implemented in 2.0.16. Ooops.
There exists a patch to have it in 2.0.16.
Birger
Russell schrieb am Mon, Apr 08, 2002 at 02:34:33PM +0100:
> Hi,
>
> I'm trying to use the alternate namespace feature, but having little joy.
>
> My /etc/imapd.conf file looks like this:
>
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> admin
s been said before that we can't have subfolders from =
the inbox when using alternate namespace - but I'd be ever so chuffed if =
we could. Why? Simply because Microsoft Exchange lets you have an IMAP =
account where you can make folders at any level - within Inbox, or at =
t
Hi,
Now, I know that its been said before that we can't
have subfolders from the inbox when using alternate namespace - but I'd be ever
so chuffed if we could. Why? Simply because Microsoft Exchange lets you have an
IMAP account where you can make folders at any level - within In
Sorry - forgot to say I'm using version
2.0.16.
- Original Message -
From: Russell
To: [EMAIL PROTECTED]
Sent: Monday, April 08, 2002 2:34 PM
Subject: Alternate Namespace
Hi,
I'm trying to use the alternate namespace feature,
but having little joy.
My /etc/imapd
e
there is any way around this?
Good news is, the alternate namespace works a
treat!
- Original Message -
From: Russell
To: [EMAIL PROTECTED]
Sent: Monday, April 08, 2002 2:43 PM
Subject: Fw: Alternate Namespace
Sorry - forgot to say I'm using version
2.0.16.
--
Hi,
I'm trying to use the alternate namespace feature,
but having little joy.
My /etc/imapd.conf file looks like
this:
configdirectory: /var/imappartition-default:
/var/spool/imapadmins: ***sasl_pwcheck_method:
sasldballowanonymouslogin: noallowplaintext: yesaltname
mapd.conf(5).
> >>
> >
> > The docs are good and should be read.
> >
> >
> > I however do see a problem between the two implementations. I have set up two
>separate imapd processes running on different ports and with different (one with
>ALTERNATE N
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 folder
a problem between the two implementations. I have set up two
separate imapd processes running on different ports and with different (one with
ALTERNATE NAMESPACE) imapd.conf files.
I am using a modified UW-imap tool (imapxfer) to transfer mail from one server to
another.
The below shows that the
stening on
port 143 and presenting the standard namespace, and an imaptest service
listening on port 9143 using its own config file and presenting the
alternate namespace.
The bottom line: if you simply install this code and change nothing,
then it will run the same as your current setup.
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 releva
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?
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-name
> On Thu, 07 Jun 2001 20:45:22 -0400,
> Ken Murchison <[EMAIL PROTECTED]> (km) writes:
km> I took a look at this and it IS doable (I actually hacked some code),
km> but it makes the LIST/LSUB code uglier than it already is. For this
km> reason, and the fact that Larry and I both feel tha
I both feel that most users won't be
sharing their INBOXes, I'm not going to implement this right now.
That being said, if the current behavior is determined to be a violation
of RFC2342 or the people that contracted me to implement the alternate
namespace want this 'feature' or deman
I just made the second (and hopefully final) beta of the alternate
namespace code available at:
ftp://ftp.oceana.com/pub/cyrus-imapd-2.0.14-NAMESPACE-r2.tar.gz
You can also grab it via anonymous CVS at CMU by checking out the
"alt-namespace" branch or "alt-namespace-r2" tag.
it's going to break a lot of other stuff,
I'll probably skip it for the time being.
In fact, I'll look at this tonight. I was just about to release a new
beta with updates to lmtpd, but I'll hold off until I check this out.
I'm interested in what other people think abou
Ken
(Message sent a few days ago but I don't think it got through).
The alternate namespace looks like a very useful enhancement that should
avoid problems with the many clients that
assume too much about what the namespace should be. I think it's also much
more in line with what us
John Holman wrote:
>
> We would like to use 2.0.14-NAMESPACE with the alternate namespace enabled.
> This works when naming a mailbox through the IMAP protocol but does not
> seem to extend to mailbox names in sieve scripts. It does mean that
> existing sieve scripts will contin
We would like to use 2.0.14-NAMESPACE with the alternate namespace enabled.
This works when naming a mailbox through the IMAP protocol but does not
seem to extend to mailbox names in sieve scripts. It does mean that
existing sieve scripts will continue to work, but it seems wrong that users
[EMAIL PROTECTED] wrote:
>
> From: "Tarjei Huse" <[EMAIL PROTECTED]>
> >
> >Hi,
> >> >One point that I failed to mention is that subfolders of INBOX are _NOT_
> >> >permitted when using the alternate namespace (subfolders of other
>
From: "Tarjei Huse" <[EMAIL PROTECTED]>
>
>Hi,
>> >One point that I failed to mention is that subfolders of INBOX are _NOT_
>> >permitted when using the alternate namespace (subfolders of other
>> >personal folders are allowed). This sacr
Hi,
> >One point that I failed to mention is that subfolders of INBOX are _NOT_
> >permitted when using the alternate namespace (subfolders of other
> >personal folders are allowed). This sacrifice had to be made in order
> >to preserve the existing mailstore structure
From: Ken Murchison <[EMAIL PROTECTED]>
>
>[EMAIL PROTECTED] wrote:
>>
>> From: Ken Murchison <[EMAIL PROTECTED]>
>> >
>> >I am pleased to announce the availability of an alternate namespace for
>> >Cyrus IMAP which allows personal
[EMAIL PROTECTED] wrote:
>
> From: Ken Murchison <[EMAIL PROTECTED]>
> >
> >I am pleased to announce the availability of an alternate namespace for
> >Cyrus IMAP which allows personal folders to reside at the same
> >[top]level as the INBOX. You shoul
From: Ken Murchison <[EMAIL PROTECTED]>
>
>I am pleased to announce the availability of an alternate namespace for
>Cyrus IMAP which allows personal folders to reside at the same
>[top]level as the INBOX. You should consider this code to be late-beta,
>
I encourage peo
I am pleased to announce the availability of an alternate namespace for
Cyrus IMAP which allows personal folders to reside at the same
[top]level as the INBOX. You should consider this code to be late-beta,
but it is fully functional and appears to be as stable as 2.0.14. I
have been running
32 matches
Mail list logo
