After wondering for a while, I can now reproduce your problems. The
only
thing I had to do was to define WORDS_BIGENDIAN on a little-endian
machine. Why are you doing that? :)
Er, you're right. I built a "fat" (multi-architecture) Dovecot
executable on a big-endian PowerPC/MacOSX machine an
On Sep 2, 2008, at 9:49 PM, CJ Keist wrote:
Sep 2 10:42:03 goku dovecot: [ID 107833 mail.crit] Panic:
IMAP(brickner): file index-mail.c: line 1091 (index_mail_close):
assertion failed: (!mail->data.destroying_stream)
Is this same bug?
No, it's a different one, but I haven't been able to repr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like I'm still getting some errors:
Sep 2 10:42:03 goku dovecot: [ID 107833 mail.crit] Panic:
IMAP(brickner): file index-mail.c: line 1091 (index_mail_close):
assertion failed: (!mail->data.destroying_stream)
Is this same bug?
Timo Sirainen
On Mon, 2008-08-25 at 18:39 +0300, Lauri Jesmin wrote:
> Hello,
>
> I upgraded dovecot to 1.1.2 this weekend and i get those errors:
> grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100|
> sort | uniq -c | sort -rn
>7547 file index-sync.c: line 39: assertion failed:
> (seq_
On Fri, 2008-08-29 at 15:03 -0500, Mike Abbott wrote:
> Panic: IMAP(user): file message-parser.c: line 684
> (preparsed_parse_next_header_init): assertion failed: (ctx->part-
> >physical_pos >= ctx->input->v_offset)
..
> (gdb) p *ctx
> $4 = {parser_pool = 0x812b638, part_pool = 0x0, input = 0x8
On Fri, 2008-08-29 at 12:58 -0500, Mike Abbott wrote:
> dovecot: Aug 29 11:24:48 Error: child 66917 (imap) killed with signal 11
>
> --- Backtrace ---
> mail_cache_header_fields_get_offset + 214
Fixed: http://hg.dovecot.org/dovecot-1.1/rev/b662b2beaf12
signature.asc
Description: This is a digi
On Fri, 2008-08-29 at 12:58 -0500, Mike Abbott wrote:
> For other users I see this error before imap crashes:
> dovecot: Aug 29 11:45:23 Error: IMAP(user2): Rebuilding index file /
> Volumes/Spool/spool/user2/mail/dovecot.index: CPU architecture changed
> Attached are pre- and post-rebuild copies
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo,
24hrs, and no errors so far. Thanks so much for the fix!!!
Timo Sirainen wrote:
> The bug was completely elsewhere than I thought. I was just about to
> send a debug patch for some of you to test, but immediately after that I
> managed to
The bug was completely elsewhere than I thought. I was just about to
send a debug patch for some of you to test, but immediately after that I
managed to reproduce it myself. :) So this should finally get rid of the
problem:
http://hg.dovecot.org/dovecot-1.1/rev/8cc0eaec7d0f
signature.asc
Descrip
Ühel kenal päeval, E, 2008-08-25 kell 10:59, kirjutas CJ Keist:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Lauri,
>This is a known bug. You can search the dovecot mailing list for
> "assertion". I'm running on Solaris 10 and see the same errors. So far
> it doesn't look to be caus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lauri,
This is a known bug. You can search the dovecot mailing list for
"assertion". I'm running on Solaris 10 and see the same errors. So far
it doesn't look to be causing my users any problems. I also did apply
the patch:
http://hg.dovecot.or
Hi folks!
>> Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0]
>> -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] ->
>> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] ->
>> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] ->
>> imap(index_t
Some minutes ago I wrote:
> after about 3 weeks without any problems, I've found this crash in
> yesterday's logfile (again related to index_mailbox_set_recent_seq):
>
> Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0]
> -> imap [0x80cf93a] -> imap [0x80cf26c] ->
On Aug 5, 2008, at 3:48 AM, Nuno Lopes wrote:
Do you still have the files? You forgot to send the
dovecot.index.log file. Also perhaps dovecot.index.cache could help
when figuring this out (but it contains message headers so you may
not want to send it to this mailing list at least).
On Jul 25, 2008, at 6:01 PM, Jon Fullmer wrote:
I saw the release notes to Dovecot-1.1.2. Some of the fixes imply
that this plus addressing anomaly that I experienced with 1.1.0 (and
1.1.1) might have been resolved with 1.1.2. Has it been?
v1.1.2 supports this:
b) Call deliver with -m INB
On Jul 24, 2008, at 9:22 PM, Nuno Lopes wrote:
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:
On Fri, 25 Jul 2008 16:01:34 -0600, Jon Fullmer <[EMAIL PROTECTED]> wrote:
> I saw the release notes to Dovecot-1.1.2. Some of the fixes imply that
> this plus addressing anomaly that I experienced with 1.1.0 (and 1.1.1)
> might have been resolved with 1.1.2. Has it been?
Plus addressing and sieve
I saw the release notes to Dovecot-1.1.2. Some of the fixes imply that
this plus addressing anomaly that I experienced with 1.1.0 (and 1.1.1)
might have been resolved with 1.1.2. Has it been?
- Jon
On Jun 22, 2008, at 9:45 PM, Tim Sirainen wrote:
The difference is that nowadays deliver sup
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: line 542 (index_sort_add_ids_ra
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: line 542 (index_sort_add_ids_range):
assertion failed: (left_idx ==
20 matches
Mail list logo
