similar to: dovecot 1.1.4 maildir imap segfault in message_parse_header_next

Hi List, try 1.1.4 and have new Panics in Log. Hoped that 1.1.3 finishes this errors... Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Loading modules from directory: /usr/lib/dovecot/imap Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Module loaded: /usr/lib/dovecot/imap/lib20_mail_log_plugin.so Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Effective uid=857, gid=628,

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

I noticed these happen when one of my users searches his Trash folder which he doesn't empty. He uses thunderbird and it is reproducable. Feb 5 22:47:39 boomhauer dovecot: IMAP(username): file message-header-parser.c: line 350 (message_parse_header_next): assertion failed: +(IS_LWSP(line->value[0])) Feb 5 22:47:41 boomhauer dovecot: child 8022 (imap) killed with signal 6 Feb 5

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

Hello, We're having a problem in Dovecot 1.1.8 with a failed assertion on certain mbox format mailboxes. It happens both with deliver when it attempts to delier to the mailbox, and with IMAP connections for the affected box (though I'm not sure what they're doing at the time). Mar 3 12:55:26 <snip> dovecot: Panic: IMAP(<snip>): file istream.c: line 81 (i_stream_read):

Hi, its me again. I still cant use any 1.1 edition because of recurrent panics... At the moment i try 1.1.7, i have again panics and problems with Next message unexpectedly lost dovecot -n # 1.1.7: /etc/dovecot.conf # OS: Linux 2.6.24.4 i686 SUSE LINUX 10.1 (i586) protocols: imap imaps pop3 pop3s ssl_ca_file: /path/path/*.servername.com.bundle.crt ssl_cert_file: /path/path/*.servername.com.crt

Hi Timo, some imap processes seems to have some problems. Regards, Pascal -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1

This is from the June 16 CVS, it also happens with June 15 but not with June 8. Basically, imap segfaults when opening my mbox. Some details are below: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x08094e5c in message_parse_header_next (ctx=0x80c8e10, hdr_r=0xbffff64c) at message-parser.c:755 755 if (msg[0] ==

Hello, I'm developing an encryption plugin for dovecot and ran into a problem with the stacking of i/o-streams. The encryption i/o-streams are working fine on any kind of mail the test suite is passing through them. But as soon as the zlib plugin is enabled the logs show an cache error: failed: Cached message size larger than expected (214 > 206, box=INBOX, UID=1) I've already

I've been getting a few of these errors on a couple different mboxes. This is using the CVS version as of May 14. So far, these are the only errors and it looks like most/all of the older ones are gone. (maybe I shouldn't say that ;-) dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:

Hi, I just added an "archive" mbox namespace to my dovecot setup, so that people can put their old mail into a slightly more inode-friendly box. When querying the STATUS on one of these boxes, I got a sigsegv: Program received signal SIGSEGV, Segmentation fault. 0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759 759

I'm encountering a crash which this command: % doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore at backup.invalid): Error: Raw backtrace:

Apart from a few warnings (attached), and a bit of patience, the compiler terminates without error. On patience, OBSD has two processes who took almost half the CPU when compiling: reaper and zerothread. Will look into the warnings, and the testing errors (also attached). Let see how it works on this machine. OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 real mem = 17125511168

Hi! I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening mailbox. The crash only triggers on opening inbox, other mailboxes seem to work fine. It happens every time, and can be reproduced on request. I also briefly tried 2.2.19, and it behaves the same. The bug seems to be triggered by some mail, as I encountered it previously and fixed by removing some spam. I

Known issue when folder cache is too big. Try rm -rf dovecot.index.cache for the folder. Aki On 24.5.2019 13.37, Ralf Hildebrandt via dovecot wrote: > I'm encountering a crash which this command: > > % doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 > > doveadm(restore at

I'm trying this: doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox "" \ mailbox INBOX header X-Spam Yes nd I'm getting: doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore at backup.invalid): Error: Raw backtrace:

Today I was looking for some spam and issued this command: ========================================================== doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox INBOX header Reply-To bixrs.com Then I immediately got a crash: doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset <

Hello! I'm using maildir format with zlib_save=bz2. Here is the way how I generate empty mails and this leads to segfault: create empty message: # echo -n "" | /usr/libexec/dovecot/dovecot-lda -d marcin at mejor.pl this creates empy email in maildir (size 14B): # ls -l 1518011524.M96165P15900.jowisz\,S\=0\,W\=0\:2\, -rwxrw----+ 1 mail mail 14 Feb 7 14:52

I just tried the latest version from CVS and got this error: dovecot: Mar 29 18:11:33 Error: 27526 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: Mar 29 18:11:33 Error: 27526 IMAP(todd.bluegenesis.com): file index-mail-headers.c: line 68

Hi, got the following with beta4 while uploading messages from a local mbox to the dovecot server in my LAN, tested with mutt and sylpheed, the same action works with 1.2.11: Mar 29 13:42:46 [dovecot] imap(juergen): Panic: stream doesn't support seeking backwards Mar 29 13:42:46 [dovecot] imap(juergen): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76b7ec4] ->