search for: index_mail_parse_bodi

Hi, I compressed a folder with the following script: ... for i in *.*.*; do file $i | grep bzip2 >/dev/null 2>&1 if [ $? -ne 0 ]; then echo "Compress: $i" cat "$i" | bzip2 -9 > ../tmp/$i if [ $? -eq 0 ]; then mv ../tmp/$i $i fi else

Panic: IMAP(user): file message-parser.c: line 684 (preparsed_parse_next_header_init): assertion failed: (ctx->part- >physical_pos >= ctx->input->v_offset) Linux 2.6.24-19-386 Maildir on ext3 Looks similar to but different from http://dovecot.org/list/dovecot/2008-June/031523.html . #0 0xb7faf410 in __kernel_vsyscall () #1 0xb7e6f085 in raise () from

Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.63-2 x86_64. Filesystem is ZFS. All the core files are similar: $ gdb

Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.63-2 x86_64. Filesystem is ZFS. All the core files are similar: $ gdb

Hi, dovecot's message parser enters an endless loop when fed with certain multipart messages with stray CR characters. parse_next_body_to_boundary() assumes the '\r' might be the beginning of a boundary line, reducing the block size by one: src/lib-mail/message-parser.c: 404 /* no linefeeds in this block. we can just skip it. */ 405 ret = 0; 406

Jun 2 10:05:14 hostname dovecot: IMAP(testuser): Panic: file istream- raw-mbox.c: line 380: assertion failed: (new_pos > 0) Jun 2 10:05:14 hostname dovecot: dovecot: child 544822 (imap) killed with signal 6 (dbx) where raise(??) at 0x90000000005a68c abort() at 0x900000000085c2c default_fatal_finish(type = LOG_TYPE_PANIC, status = 0), line 160 in "failures.c"

Hi, Today's core dump from 1.0alpha1 came from a syslog message of: IMAP(user): pool_data_stack_realloc(): stack frame changed gdb info on the resulting core dump attached. Question: how many people are building/using dovecot 1.0alpha1 with gcc 4.0.1 versus gcc 3.4.x? I am wondering if these issues come from the compiler instead of dovecot itself? Jeff Earickson Colby College