similar to: assert with zlib and (maybe) fts

Hi, My setup: Solaris 9, mbox format, mailboxes NFS mounted from another S9 system, imap. I got the following assert yesterday: Jan 30 19:57:15 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) Jan 30 19:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line

> > Is this behavior cured, or do you continue to see it? > No, the behavior isn't cured. We still continue to see it with various clients. I have posted a couple of truss outputs, but so far no resolution. Sorry for the slow response. I've been "fighting other fires". Jackie > Jackie Hunt wrote: > >> On Mon, 2007-09-03 at 12:37 +0200, Robert

Hi all, ive seen a few segfaults in RC15. It's hard for me to reproduce but I was able to get a core when it happened with one of our customers. RC15 FreeBSD 4.10 X86 NFS/NetApp It's squirrelmail/webmail client. Can't reproduce it, cant turn on dovecot.rawlog because I dont know in advance which customer will hit this. See it about 5 times per hour, with thousands of logins per hour.

I found imap core in coredump dir: (gdb) bt #0 0x00000000004abdea in message_parse_header_next (ctx=0x79c150, hdr_r=0x7fffffffe478) at message-header-parser.c:114 #1 0x00000000004a8193 in read_header (mstream=0x795330) at istream-header-filter.c:162 #2 0x00000000004a84e7 in i_stream_header_filter_read (stream=0x795330) at istream-header-filter.c:288 #3 0x00000000004bc216 in i_stream_read

Here is the first crash I've seen with the current CVS... Feb 19 00:45:52 mail35a dovecot: IMAP(mnash at stest1.com): Corrupted transaction log file /var/index//data1/mail/st/stest1.com/mn/mnash//.Trash/dovecot.index.log: Append with UID 5736, but next_uid = 5744 Feb 19 00:45:55 mail35a dovecot: IMAP(mnash at stest1.com): Corrupted transaction log file

Hi Benjamin: I think that the following link will give you an idea for what you need to know: http://www.cisco.com/warp/customer/620/roadmap_b.shtml This is for the naming: http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not you worry you will not loose anything with the new

I have a situation where if a user is over quota and sending through postfix I get an error, now this error only happens if the user is over quota, otherwise it works with no problem. However if sending using /usr/local/libexec/dovecot/dovecot-lda it works every time even if overquota, any ideas? I just can't seem to figure this one out. TIA, Paul Using mail command Dec 21

I've tried to stress test dovecot 1.1.4 with imaptest for days without any assertion failure or crash. Just some "got too little data" messages. So far it's the most stable 1.1.x version. Today a user got this imap segfault with vanilla 1.1.4 (I don't know if it's something you have already fixed in current tree). The user didn't complain of anything, I've just

Greetings, I recently upgraded our server from Dovecot 1.0.14 to 1.1.1. I am building using the FreeBSD ports system, so nothing is custom aside from the flags set there. dovecot fell down a few days after the update with: pid 1823 (imap), uid 1000: exited on signal 11 the mail log shows: Jul 4 14:36:07 hostname dovecot: IMAP(username): Corrupted index cache file

Hi, dovecot crashes with the following trace when accessing some Maildirs: dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): file index-mail-headers.c: line 260 (index_mail_parse_header): assertion failed: (part != NULL) dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): Raw backtrace: imap [6126360] [0x80b6d6b] -> imap [6126360] [0x80b6769] -> imap [6126360] [0x808abda]

http://dovecot.org/test/ - vpopmail authentication fix - many mmap_disable=yes fixes and a few optimizations - pop3 hang fix - mbox fix for "last-uid lost" error (hopefully last one) - mbox fix for losing dirty flag, causing lost message flags mmap_disable=yes seems to be finally working pretty well. There should be no more cache file related errors with it enabled. I'm still

I am running 1.1.beta11 because I was having locking and coruption issues with indexes and mailbox on the latest release version. Some of my previous corrupted indexes caused an issue with 1.1.beta11: Dec 20 21:25:40 ra dovecot: IMAP(bodil at mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap

This is 1.0.13, the processes crashed a few seconds apart from each other: GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show

I've not been able to roll out rc23 yet (tonight, I hope) but I just saw a crash which I'm not sure I've seen reported before, following a server outage (that is to say, the server came back up and one of the users had a dovecot core). #0 0x0005d720 in mail_cache_transaction_reset (ctx=0xcf928) at mail-cache-transaction.c:71 No locals. #1 0x0005e8bc in mail_cache_add

Today I updated to current dovecot-1.1 hg tree and I got many of these assertion failures: file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (gdb) bt full #0 0x00352402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6

I've attached two backtraces, one from a segfault and another from an assertion error in imap. I've seen a couple of the same assertion and this is the only segfault. It looks like they could be related. They both have to do with indexing anyway... The code is from CVS as of May 30. The segfault happened while imap was doing searches for my pine filters. I've also noticed that in

Hello! I just installed Dovecot's latest nightly build (20081020) and tried the virtual folder features. I started with a really simple "all" folder: | # virtual/all | * | all But selecting this folder causes dovecot to panic (in most cases). While trying to debug this, I got slightly different results and I am not really sure yet if this is just non-deterministic, depends on

I'm running the CVS version from May 9. I've seen these errors in the log file before (every time I open my mailbox), but this is the first time it crashed. Todd dovecot: May 11 15:00:18 Error: 8438 IMAP(todd.bluegenesis.com): Corrupted index cache file /mailhome/new/t/b/todd.bluegenesis.com/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: May 11

Found a new segfault in imap. The first log entry always happens on my mailbox, but doesn't seem to affect anything. This is CVS version from Aug. 15. dovecot: Aug 21 17:16:56 Error: 28017 IMAP(todd): Corrupted index cache file /mailhome/new/t/b/todd/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Aug 21 17:19:44 Error: child 28017 (imap) killed with

Occasionally, while reading the headers of a folder, Dovecot crashes. The visible effect in my mail client is that it will tell me a folder has a new message, but when I click on it, it will take forever to load, and there will be no new messages. When another message comes in to that folder, the folder begins to work again. I generated a core from the latest crash, and the gdb dump is included