The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 2.4.19.
This is a bug fix release for the old 2.4 series. It should not be used
for new Cyrus installations, but may be useful to administrators of 2.4
systems who are not yet able to migrate to 3.0.
Hi Sandra,
The issue you linked to was due to an issue with some sieve scripts. The
administrator tried compiling the system scripts by hand using sievec to
work out which ones were no good. They were then removed/fixed.
This documentation tells you how to enable core dumps:
Hello everybody,
I am trying to upgrade my cyrus-2.4.17 to cyrus-3.0.1 but I have
found some problems with lmtp segfaults as
described some time ago in this info-cyrus thread
https://lists.andrew.cmu.edu/pipermail/info-cyrus/2015-November/038585.html
I want to know it this problem
My imapd.conf has no mention of the database formats. I'm using Debian, and I
believe that info is supposed to be in /usr/lib/cyrus/cyrus-db-types.active.
I don't have that file either because the Debian instructions say to delete
that file when you change the database format, putting
the new
Hello,
I've got the following in the sieve script
elsif header :matches "subject" "[proxy] File-URL (*) detected"
{
fileinto "INBOX._Info.ftpFileURLs";
}
else
{
fileinto "INBOX._Info";
}
when the subject is e.g.
[proxy] File-URL (Media-PC) detected
then the if is true, this correct
Am Montag, den 15.05.2017, 07:59 -0300 schrieb Patrick Boutilier:
> rm -fr if you are 100% sure you don't need the files. Move if not 100%
> sure .:-)
>
> Since cyrus doesn't know about the folders in mailboxes.db it shouldn't
> care either way.
That's working.
Thanks
Marcus
Cyrus Home
--On 15. Mai 2017 um 20:16:56 + "Boylan, Ross"
wrote:
I am upgrading an old cyrus 2.2 installation to 2.4. Using a chroot I
converted all my old bdb databases to skiplist and copied the results to
the system with cyrus 2.4. cyrus2.4 wouldn't not start, giving lots