Re: Hello cyrus users

2008-04-24 Thread Simon Matter
I am not sure how happy I am too find out about cyrus. I just spent a lot of time getting everythig working on my first server...and even sendmail was not too hard (centos 5 sets it up rather well)... Then I see I needed a pop3 doo hickey.. Holy moly. Looking for cyrus on machine was

Re: Hello cyrus users

2008-04-24 Thread Sebastian Hagedorn
--On 24. April 2008 09:06:33 +0200 Simon Matter [EMAIL PROTECTED] wrote: Holy moly. Looking for cyrus on machine was interesting as almost all of the files would not come up with a 'locate' command. And still do not. I am manually going through all the doc folders and etc and sys folders

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Thomas Robers
Andy Fiddaman schrieb: That's the line that the patch changes, and that's the old version of the line, so something didn't take with your patching. A. It seems so, but I don't understand, why. Here's the patch: --- cyrus-imapd-2.3.12/lib/libconfig.c 2008/04/11 20:07:00 1.18 +++

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Gabor Gombas
On Thu, Apr 24, 2008 at 09:58:05AM +1000, Bron Gondwana wrote: Have you looked at: http://cyrus.brong.fastmail.fm/patches/cyrus-auditlog-2.3.11.diff It's a very detailed logging system which logs all create, delete, append, copy, expunge, unlink, etc events. Anything which changes a

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
Andy Fiddaman schrieb: That's the line that the patch changes, and that's the old version of the line, so something didn't take with your patching. A. It seems so, but I don't understand, why. Here's the patch: --- cyrus-imapd-2.3.12/lib/libconfig.c 2008/04/11 20:07:00 1.18 +++

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
Simon Matter schrieb: They don't apply togheter, only one can be applied. Try with fresh sources and Andy Fiddaman's patch should apply fine. Simon I should have mentioned that that I did it with fresh sources. 1. fresh sources with first patch 2. delete source tree 3. unpack sources

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Thomas Robers
Simon Matter schrieb: They don't apply togheter, only one can be applied. Try with fresh sources and Andy Fiddaman's patch should apply fine. Simon I should have mentioned that that I did it with fresh sources. 1. fresh sources with first patch 2. delete source tree 3. unpack sources and

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Thomas Robers
Simon Matter schrieb: Did you copy/paste the patch? Then maybe it's a problem with whitespace and such. Can you try the attached one. Yes I did c/p and that seems to be the problem, because with your patch it did that: imap-1:/export/build/cyrus-imapd-2.3.12# patch -p1

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
Simon Matter schrieb: Did you copy/paste the patch? Then maybe it's a problem with whitespace and such. Can you try the attached one. Yes I did c/p and that seems to be the problem, because with your patch it did that: imap-1:/export/build/cyrus-imapd-2.3.12# patch -p1

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
I am pleased to announce the release of Cyrus IMAPd 2.3.12. This release should be considered production quality. Noteworthy changes: * Added statuscache.db to cache IMAP STATUS data which significantly reduces the amount of I/O necessary when neither the mailbox nor \Seen state has

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Ken Murchison
Simon Matter wrote: I am pleased to announce the release of Cyrus IMAPd 2.3.12. This release should be considered production quality. Noteworthy changes: * Added statuscache.db to cache IMAP STATUS data which significantly reduces the amount of I/O necessary when neither the mailbox nor

Re: Hello cyrus users

2008-04-24 Thread Alain Spineux
On Thu, Apr 24, 2008 at 9:06 AM, Simon Matter [EMAIL PROTECTED] wrote: I am not sure how happy I am too find out about cyrus. I just spent a lot of time getting everythig working on my first server...and even sendmail was not too hard (centos 5 sets it up rather well)... Then I

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
Simon Matter wrote: I am pleased to announce the release of Cyrus IMAPd 2.3.12. This release should be considered production quality. Noteworthy changes: * Added statuscache.db to cache IMAP STATUS data which significantly reduces the amount of I/O necessary when neither the mailbox nor

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Ken Murchison
Simon Matter wrote: Simon Matter wrote: I am pleased to announce the release of Cyrus IMAPd 2.3.12. This release should be considered production quality. Noteworthy changes: * Added statuscache.db to cache IMAP STATUS data which significantly reduces the amount of I/O necessary when

Re: Cyrus IMAPd 2.3.12 Released

2008-04-24 Thread Simon Matter
Simon Matter wrote: Simon Matter wrote: I am pleased to announce the release of Cyrus IMAPd 2.3.12. This release should be considered production quality. Noteworthy changes: * Added statuscache.db to cache IMAP STATUS data which significantly reduces the amount of I/O necessary when

Cyrus IMAPd 2.3.12p1 Released

2008-04-24 Thread Ken Murchison
I am pleased to announce the release of Cyrus IMAPd 2.3.12p1. This release should be considered production quality. The only change from 2.3.12 is a patch to fix a memory corruption in the imapd.conf parsing code which could cause segfaults on certain platforms. Noteworthy changes from 2.3.11:

Cyrus IMAPd 2.3.12p2 Released

2008-04-24 Thread Ken Murchison
I am pleased to announce the release of Cyrus IMAPd 2.3.12p2. This release should be considered production quality. I was careless in applying the memory corruption patch in 2.3.12p1 and it didn't actually solve the problem. It should be fixed now. Noteworthy changes from 2.3.11: * Added

Re: Cyrus IMAPd 2.3.12p2 Released

2008-04-24 Thread Simon Matter
I am pleased to announce the release of Cyrus IMAPd 2.3.12p2. This release should be considered production quality. I was careless in applying the memory corruption patch in 2.3.12p1 and it didn't actually solve the problem. It should be fixed now. Ken, I can't see any difference between