Re: Sieve service terminated abnormally

2014-02-28 Thread Fabio S. Schmidt
Hi Adam ! Thanks for the answer. The users are not complaining about the Sieve service and the clients are able to connect after these messages. Sorry, I didn't understand what you said about a core file. On 28 February 2014 18:40, Adam Tauno Williams wrote: > On Thu, 2014-02-27 at 15:34 -0300

Re: Ubuntu 13.10 | Cyrus 2.4 IMAPd | Specs Folders

2014-02-28 Thread Fabio S. Schmidt
Hi Andrew, thanks for sharing your experience here ! We use Cyrus 2.4.14 and are planning to update to 2.4.17 soon, and autocreate would be really useful for us, does anyone know if it works with Aggregator? Some time ago I have downloaded the autocreate patch for cyrus 2.4.12 and it worked on 2.4

Re: Sieve service terminated abnormally

2014-02-28 Thread Adam Tauno Williams
On Thu, 2014-02-27 at 15:34 -0300, Fabio S. Schmidt wrote: > I'm running Cyrus 2.4.14 with Aggregator and this messages appears > several times on my frontend logs: > service sieve pid 10238 in BUSY state: terminated abnormally I have not seen that message. Do you end up with a core file? > Wh

Re: Backend reboot replication lost

2014-02-28 Thread Michael Menge
Hi Quoting Willy Offermans : Dear cyrus friends, Once more my backend server was rebooted. I did not find any messages in my logs nor did I receive any screen messages, that the replication was stopped. I wonder what will happen in a production environment, when the server reboots without my n

Re: Outlook 2013

2014-02-28 Thread Adam Tauno Williams
On Thu, 2014-02-27 at 21:58 +0100, Paul van der Vlis wrote: > I would like to tell that I got some private mails telling that Outlook > 2013 does not work well with imap. I have several users using Outlook with Cyrus IMAPd; it works without issue. At least from 2003 and later. One tip is to d

Backend reboot replication lost

2014-02-28 Thread Willy Offermans
Dear cyrus friends, Once more my backend server was rebooted. I did not find any messages in my logs nor did I receive any screen messages, that the replication was stopped. I wonder what will happen in a production environment, when the server reboots without my notice. Replication will fail and