> 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 r
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
> 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
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 th
> 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
> 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 <
>> ../
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 <
> ../cyrus-imapd
> 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
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
> 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:
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
>
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
>
Hi!
Bron Gondwana wrote:
>> + copyargs->name, index_getheader(mailbox, msgno,
>> "X-DSPAM-Signature"));
>
> Wow - that's pretty tricky. I see you're actually logging a specific
> header as well. Funky. We don't have anything like that in our
yes.
> I'd still suggest that this should b
>
>
> On Wed, 23 Apr 2008, Thomas Robers wrote:
>
> ; Ken Murchison schrieb:
> ; > Can you try this patch:
> ; >
> ; >
> https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/lib/libconfig.c.diff?r1=1.18;r2=1.18.2.1
> ;
> ; I tried the patch. Compiling is ok, but the master segfaults when I
On Wed, Apr 23, 2008 at 03:37:19PM +0400, Dmitriy Kirhlarov wrote:
> If dspam miss, user can manually move message from|to "spam" folder. This
> fact fixed in cyrus log file. simple script parsing log and relaunch dspam.
> +syslog(LOG_ERR, "DSPAM-Hack index_copysetup(): %s -> %s, hdr %s",
>
On Wed, Apr 23, 2008 at 05:58:27PM +0400, Dmitriy Kirhlarov wrote:
> Sebastian Hagedorn wrote:
> > --On 23. April 2008 15:37:19 +0400 Dmitriy Kirhlarov <[EMAIL PROTECTED]>
> > wrote:
> >
> >> Attached patch add to log information about moving messages between
> >> folders. I am using this informa
Sebastian Hagedorn wrote:
> --On 23. April 2008 15:37:19 +0400 Dmitriy Kirhlarov <[EMAIL PROTECTED]>
> wrote:
>
>> Attached patch add to log information about moving messages between
>> folders. I am using this information from logs for relaunch dspam.
>> Any chances for add this patch to project
On Wed, 23 Apr 2008, Thomas Robers wrote:
; Ken Murchison schrieb:
; > Can you try this patch:
; >
; >
https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/lib/libconfig.c.diff?r1=1.18;r2=1.18.2.1
;
; I tried the patch. Compiling is ok, but the master segfaults when I try to
start:
; 3
--On 23. April 2008 15:37:19 +0400 Dmitriy Kirhlarov <[EMAIL PROTECTED]> wrote:
Attached patch add to log information about moving messages between
folders. I am using this information from logs for relaunch dspam.
Any chances for add this patch to project tree?
FWIW, logging this at LOG_ERR l
Ken Murchison schrieb:
> Can you try this patch:
>
> https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/lib/libconfig.c.diff?r1=1.18;r2=1.18.2.1
>
I tried the patch. Compiling is ok, but the master segfaults when I try to
start:
This GDB was configured as "x86_64-linux-gnu".
(gdb) f
Attached patch add to log information about moving messages between
folders. I am using this information from logs for relaunch dspam.
Any chances for add this patch to project tree?
It's useful schema and I think it can be helpful not only for me.
Some details:
dspam watch all incoming message
Hi,
thanks for the answer
Bron Gondwana schrieb:
> This would be even more useful:
>
> % gdb /opt/imap/libexec/master
>> run -d
> [ wait for it to segfault ]
>> bt
here's the output
(gdb) file /opt/imap/libexec/master
Reading symbols from /opt/cyrus-imapd-2.3.12/libexec/master...done.
Using ho
On Mon, 21 Apr 2008, Ken Murchison wrote:
> I don't have an OpenBSD system to test on, and I don't have any problem on
> Linux or Solaris. I'd be happy to accept a patch if you can find the problem.
This patch fixes the issue for me:
http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3059
--
Antoi
On Wed, 23 Apr 2008 10:33:27 +0200, "Thomas Robers - TuTech Innovation GmbH"
<[EMAIL PROTECTED]> said:
> Ken Murchison schrieb:
> > I am pleased to announce the release of Cyrus IMAPd 2.3.12. This
> > release should be considered production quality.
>
> I'm getting a segmentation fault when I try
Andy Fiddaman schrieb:
> ; On Wed, 23 Apr 2008, Thomas Robers - TuTech Innovation GmbH wrote:
> ; ; Hello,
> ; ;
> ; ; I'm getting a segmentation fault when I try to start the master process.
> ; ; Compiling went fine on Debian etch (2.6.18-5-xen-amd64) with gcc version
> ; ; (GCC) 4.1.2 20061115 (
; On Wed, 23 Apr 2008, Thomas Robers - TuTech Innovation GmbH wrote:
; ; Hello,
; ;
; ; I'm getting a segmentation fault when I try to start the master process.
; ; Compiling went fine on Debian etch (2.6.18-5-xen-amd64) with gcc version
; ; (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
;
; T
On Wed, 23 Apr 2008, Thomas Robers - TuTech Innovation GmbH wrote:
; Hello,
;
; I'm getting a segmentation fault when I try to start the master process.
; Compiling went fine on Debian etch (2.6.18-5-xen-amd64) with gcc version
; (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Take a look at h
Ken Murchison schrieb:
> 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
Antoine Jacoutot wrote:
> On Mon, 21 Apr 2008, Ken Murchison wrote:
>
>> I am pleased to announce the release of Cyrus IMAPd 2.3.12. This
>> release should be considered production quality.
>
> I'm getting a regression here:
>
> (gdb) run
> Starting program: /usr/local/libexec/cyrus-imapd/maste
On Mon, 21 Apr 2008, Ken Murchison wrote:
> Is this a clean build and a fresh restart?
Yup...
--
Antoine
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Is this a clean build and a fresh restart?
Antoine Jacoutot wrote:
> On Mon, 21 Apr 2008, Ken Murchison wrote:
>
>> I am pleased to announce the release of Cyrus IMAPd 2.3.12. This
>> release should be considered production quality.
>
> I'm getting a regression here:
>
> (gdb) run
> Starting
On Mon, 21 Apr 2008, Ken Murchison wrote:
> I am pleased to announce the release of Cyrus IMAPd 2.3.12. This
> release should be considered production quality.
I'm getting a regression here:
(gdb) run
Starting program: /usr/local/libexec/cyrus-imapd/master
Program received signal SIGSEGV, Segm
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 changed --
33 matches
Mail list logo
