similar to: imap crash

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'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

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

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

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:

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

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:

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 <

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 Aki, debian jessie backports has been moved to archive.debian.org and initially I was unable to install dovecot-dbg because of that. But I've managed to resolve that issue now. This was the command I ran: doveadm -D -f flow fetch imap.envelope mailbox crm-spam.2008.g Backtrace follows. Jason jason at debian:~$ gdb /usr/bin/doveadm /home/jason/core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1

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

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'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, 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

Oct 21 10:04:05 alchemy dovecot: imap-login: Login: user=<paulproteus>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS Oct 21 10:05:44 alchemy dovecot: IMAP(paulproteus): file message-decoder.c: line 289 (message_decode_body): assertion failed: (pos < input->size) Oct 21 10:05:44 alchemy dovecot: IMAP(paulproteus): Raw backtrace: imap [0x80c8e10] -> imap [0x80c8d1c] ->

Hello R Community, I've been working on a project that uses pre-made C++ libraries (using STL) in R and build a package. However, I've been getting an unusual segfault that I'm unable to trace its origin. After many attempts of debugging using gdb, commenting out parts (or all of my code) and valgrind, I'm unable to make heads or tails about what I'm doing wrong. In fact, when

After some investigation, it turns out it is non trivial to install dovecot-dbg on debian jessie. Sorry I can't investigate further. Jason Aki Tuomi wrote on 25/3/19 6:12 pm: > Can you install dovecot-dbg and try gdb again? > > Aki > > On 25.3.2019 3.20, Jason Lewis via dovecot wrote: >> Hi, >> >> I've been having an issue with the indexer giving me

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] ->