Displaying 9 results from an estimated 9 matches for "message_parser_parse_bodi".
Did you mean:
message_parser_parse_body
2008 Dec 10
2
assert with zlib and (maybe) fts
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
2008 Jul 25
0
Dovecot 1.1.2, SIGABRT on copy mail
Hi folks,
with the brandnew release Dovecot 1.1.2, the daemon killed itself
with signal 6 (SIGABRT) when trying to save a mail from the INBOX
to another folder. The mail client is PINE 4.64. After reconnecting
to the IMAP server, the mail was actually copied to the destination
folder, but the original mail was still in the INBOX and not flagged
as "deleted".
This is the panic:
Jul 25
2019 Oct 18
2
Coredump v2.3.8 specific msg fetch, corrupted record in index cache, Broken physical size
Hi, i'm getting a coredump on a specific msg, i've attached the gdb.
file on disk i noticed W=<vsize> is missing.
1571209735.M744550P1608.rwvirtual65,S=15886:2,S
Best regards,
mail.log
Oct 18 14:41:39 rwvirtual10 dovecot:
imap(johndoe at company.nl)<15868><qjTFpy6VPsMKAAok>:
Error: Mailbox INBOX.Debug: UID=1041: read(/data/mail/
2008 Aug 29
1
Dovecot-1.1.2 assertion failure in preparsed_parse_next_header_init
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
2013 Nov 05
1
Message parser loops on certain messages (e.g. with a trailing CR character)
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
2009 Jun 02
2
Panic with signal 6 core dump with revision 9116:9ae55b68cf61
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"
2014 Jul 06
1
Panic: file istream.c: line 167 with 2.2.13 + istream.c/.h from dovecot-2-2-dffc6dd2be0d
Hi,
Getting following panics with traces:
Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Cached message
size smaller than expected (1782 < 1872)
Jul 6 08:11:52 dovecot: imap(user at domain.tld): Error: Maildir filename
has wrong S value, renamed the file from
/path/cencored/Maildir/cur/1201713258.3136.host.cencored.fi,S=1782:2,S
to
2005 Sep 09
1
1.0alpha1: stack frame core
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
2008 Jul 02
5
litte problems upgrade from 1.0.x to 1.1.1
Hi List,
last time i did a lot of packaging and installing different versions of
dovecot 1.0.x (rc not included ;) )and all was fine.
Now a have a little problem. In this case it was an update from 1.0.13 to
1.1.1
Sometime it happens that 1 user out of x (more than 100) got this
standardmessage for ~1 or ~2 thousend times in his mailbox (mbox)
for example:
>From MAILER_DAEMON Mon Sep 18