Paul,
To add on top of what Bron said, xlist was removed in 2.5 but added as a
(somewhat?) new implementation in 3.0, so you should install the newest
version of Cyrus to take advantage of this feature.
In 3.0 xlist is part of autocreate functionality, i.e. an appropriate
flag is set on each
Hi Paul,
In newer versions the support is more accurately to spec, where you
create with (USE \Foo) and then it's stored alongside that mailbox, even
if it's renamed. The old 2.4 version was just a hack for XLIST before
the standards support was added.
Cheers,
Bron.
On Fri, Jun 15, 2018, at 01
Hello Jean-Christophe,
Am 14.06.2018 um 18:44 schrieb Jean-Christophe Delaye:
I have spent several days working in trying to have a running murder
configuration using Cyrus Imap 3.0.x on Solaris 11.3.
I checked and installed the required software components (gcc and
tools). Everything is compli
I have spent several days working in trying to have a running murder
configuration using Cyrus Imap 3.0.x on Solaris 11.3.
I checked and installed the required software components (gcc and
tools). Everything is compliling and installing fine, but I have issue
with mupdate process specially fro
Hello,
Does Cyrus IMAP support RFC 6154 about special-use mailboxes?
https://tools.ietf.org/html/rfc6154
I read that it only wass supported in Cyrus version 2.4 ?
I am using version 2.5.10 (from Debian 9).
Can I put this in imapd.conf for all users?
xlist-archive: Archives
xlist-drafts: Drafts
x
On 13/06/2018 21:48, Albert Shih wrote:
Hi eveyone
I got a server (FreeBSD + Cyrusimap, 192Go) I need to reserve some RAM for the
ZFS arc.
I would like to know how many Ram I need to run cyrus-imap.
I got on between 300-1600 connexion imap simultaneous (on my old server)
Through ps aux I s