Cyrus IMAP 3.0.1 released

2017-04-19 Thread ellie timoney
The Cyrus team is proud to announce the immediate availability of a new version of Cyrus IMAP: 3.0.1 This is a bug fix release for the 3.0 series. Download URLs: http://www.cyrusimap.org/releases/cyrus-imapd-3.0.1.tar.gz http://www.cyrusimap.org/releases/cyrus-imapd-3.0.1.tar.gz.sig

Re: IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Boutilier
On 04/19/2017 01:14 PM, Patrick Goetz wrote: Correction: just realized I'm running 2.5.7, not 2.4.17. Probably just need to upgrade, but am still interested in knowing if there is any way to get around using cyradm for adding users. We use this perl module with a very simple perl script to

Re: IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Goetz
Correction: just realized I'm running 2.5.7, not 2.4.17. Probably just need to upgrade, but am still interested in knowing if there is any way to get around using cyradm for adding users. On 04/19/2017 11:12 AM, Patrick Goetz wrote: I'm running cyrus 2.4.17 on a couple of Arch linux

IMAP.c: loadable library and perl binaries are mismatched

2017-04-19 Thread Patrick Goetz
I'm running cyrus 2.4.17 on a couple of Arch linux servers, and Arch is an aggressively updated rolling release distro. I don't have to add new users very often, but ran cyradm today and got the following error message: [root@www sbin]# cyradm --user administrator localhost IMAP.c: loadable

Re: Error: same message appears twice

2017-04-19 Thread Robert Stepanek
On Wed, Apr 19, 2017, at 10:51, Frederik Himpe wrote: > Sometimes I see in the logs messages like this: "same message appears  > twice 2394 2395". Looking at the source code, it does not appear to be > a big problem, but I am not sure. Does this indicate a real problem? > Should I run

Error: same message appears twice

2017-04-19 Thread Frederik Himpe
Sometimes I see in the logs messages like this: "same message appears  twice 2394 2395". Looking at the source code, it does not appear to be a big problem, but I am not sure. Does this indicate a real problem? Should I run cyrreconstruct on the affected mailbox, and which options do you