Re: [Dovecot] 1.1.3 vs 1.1.2 stability?

Forgot to post this to the list (once again :-/) I've been running 1.1.3 for one day on a setup similar and must say it is a clear improvement on 1.1.2. Even though there is one small assertion problem left that I'll report later as soon as I have more detail on it. Tomasz K Jarzynka wrote: Hi,

[Dovecot] version 1.1.3 assertion on index-sort-string

the index files as they were when this error happened. Thanks, -- Nuno Lopes

Re: [Dovecot] dovecot 1.1.2 assertion

Here go the files Timo Sirainen wrote: On Jul 25, 2008, at 2:36 AM, Nuno Lopes wrote: I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: lin

[Dovecot] dovecot 1.1.2 assertion

Hi, I've upgraded to last version of dovecot and am now getting the following assertions: Jul 25 00:00:34 bld3 dovecot: Panic: IMAP([EMAIL PROTECTED]): file index-sort-string.c: line 542 (index_sort_add_ids_range): assertion failed: (left_idx == 0 && right_idx == rightmost_idx) Jul 25 00:0

Re: [Dovecot] Dovecot antispam (X-DSPAM-Signature)

Hi Hugo, I'll have a look into that one. For some strange reason I hadn't seen things that way. Thanks both to you and Johannes, -- Nuno Lopes Hugo Monteiro wrote: I recently installed an IMAP server with dovecot and the dovecot antispam plugin with dspam backend. If I configur

Re: [Dovecot] Dovecot antispam (X-DSPAM-Signature)

this should be done. Thanks, -- Nuno Lopes

Re: [Dovecot] zlib plugin nad moving mails, bug?

This was a bug in version 1.0 which is now corrected in version 1.1.rc6 by looking at the file header instead of the Z flag. http://dovecot.org/pipermail/dovecot-news/2008-May/69.html Regards, -- Nuno Mateusz Kijowski wrote: Hi, Recently I gzipped mails older than 30 days in our users'

Re: [Dovecot] assertion after upgrading to 1.1rc7 from 1.1rc3

Hi, this seems to have done it! I've applied the former patch as well as these ones to all our servers and haven't seen that error for over an hour. Thanks, -- Nuno Lopes Timo Sirainen wrote: > On Thu, 2008-06-05 at 15:01 +0100, Nuno Lopes wrote: > >> Hi, >>

[Dovecot] assertion after upgrading to 1.1rc7 from 1.1rc3

Hi, I'm getting this assertion after making an upgrade from 1.1rc3 to 1.1rc7. Deleting the index files solves the problem. This seems to happen only to some accounts but I haven't managed to find which ones. I'm using dovecot's deliver to deliver the messages. Panic: IMAP([EMAIL PROTECTED]): f

Re: [Dovecot] Imap assertion (dovecot-1.1.beta13)

rule3: INBOX.Trash:storage=102400 Thanks, -- Nuno Lopes

Re: [Dovecot] Imap assertion (dovecot-1.1.beta13)

Timo Sirainen wrote: > On Mon, 2008-01-07 at 15:38 +0000, Nuno Lopes wrote: > >> Hi, >> I continue testing the beta versions and have seen a great improvement >> over the last few ones. >> On beta13 I'm seeing the following assert on some client folde

[Dovecot] Imap assertion (dovecot-1.1.beta13)

u need I can try and reproduce this in a more controled environment to pinpoint the problem. Thanks, -- Nuno Lopes

Re: [Dovecot] assertion on deliver (1.1.beta10)

Hi, it seemed to correct that one but it gave me this one in return ;-): file mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node): assertion failed: (len <= ctx->parent_pos) Thanks, -- Nuno Lopes Timo Sirainen wrote: > On Fri, 2007-12-21 at 17:19 +0200, Timo Sirainen wrote: &

Re: [Dovecot] dovecot deliver errors

Hi Andrew, I've mentioned this a few days ago and now I found out that this happens when the user would go over quota. I also use maildir and the quota plugin. I hope this helps a little more. Nuno Lopes Andrew Garner wrote: > I think someone else mentioned this problem earlier on

[Dovecot] assertion on deliver (1.1.beta10)

his in a more controled environment to pinpoint the problem. Thanks, -- Nuno Lopes