On Thu, 08 Feb 2007, Jules Agee wrote:
> All it does is process all child processes' messages at once instead of
> only processing one message per master loop (to make sure master's
Heh, stock cyrus 2.1 message passing is *nothing* like what is in Debian. I
believe cyrus 2.2 is quite similar, tho
I have a healthy MIT Kerberos 1.5.2 realm and Cyrus IMAP 2.2.12
server configured (SASL 2.1.22).
I can't get Thunderbird (latest 1.5 official release) to perform
GSSAPI authentication against the Cyrus IMAP server.
I have valid Kerberos 5 credentials (for user jblaine) via Kerberos
for Windows 3
Henrique de Moraes Holschuh wrote:
> And, if I remember it right, it needs a modified cyrus 2.1 to work (i.e.
> Debian's). I don't really know if it is working fine on 2.2 or 2.3, I lost
> track of this :(
O RLY?
All it does is process all child processes' messages at once instead of
only proces
> I am pleased to announce the release of Cyrus IMAPd 2.3.8. This release
> should be considered production quality. This release (minus
> replication) is currently deployed on the production Murder at CMU,
> and the replication code is deployed in production at several other
> large sites.
>
> P
Simon Matter wrote:
I am pleased to announce the release of Cyrus IMAPd 2.3.8. This release
should be considered production quality. This release (minus
replication) is currently deployed on the production Murder at CMU,
and the replication code is deployed in production at several other
large
Oliver Falk wrote:
Am 2007-02-07 21:29, Ken Murchison schrieb:
> I am pleased to announce the release of Cyrus IMAPd 2.3.8. This release
> should be considered production quality. This release (minus
> replication) is currently deployed on the production Murder at CMU,
> and the replication
Am 2007-02-07 21:29, Ken Murchison schrieb:
> I am pleased to announce the release of Cyrus IMAPd 2.3.8. This release
> should be considered production quality. This release (minus
> replication) is currently deployed on the production Murder at CMU,
> and the replication code is deployed in pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JFYI, replying to my own mail:
I've just upgraded the below mentioned backend to 2.3.8. The acl compatibilty
issues have been fixed just fine. The new 2.3 backend within the existing 2.1
murder works great now.
Since I have some uppercase mailboxes
