search for: message_parse_header_next

Displaying 20 results from an estimated 42 matches for "message_parse_header_next".

2008 Feb 06
2
(message_parse_header_next): assertion failed:, +(IS_LWSP(line->value[0])) 1.1beta14
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 22:48:21 boomhauer dovecot: IMAP(username): file message-header-parser.c: line 350 (message_parse_header_next): assertion failed: +(IS_LWSP(line->value[0])) Feb...
2008 Oct 16
2
dovecot 1.1.4 maildir imap segfault in message_parse_header_next
...hing you have already fixed in current tree). The user didn't complain of anything, I've just found the error in the logs and the core file. Regards, Diego. ---- Core was generated by `/usr/libexec/dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x080c8d41 in message_parse_header_next (ctx=0x8774fa0, hdr_r=0xbfa438e0) at message-header-parser.c:114 114 if (msg[0] == '\n' || (gdb) bt full #0 0x080c8d41 in message_parse_header_next (ctx=0x8774fa0, hdr_r=0xbfa438e0) at message-header-parser.c:114 msg = (const unsigned char *) 0x0...
2008 Sep 18
2
dovecot 1.1.3 coredump
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...
2016 Dec 15
0
imap Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 on Fedora 24
...717) [0x7ff01ecd4717] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xbe952) [0x7ff01ecd4952] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7ff01e997653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7ff01e99807d] -> /usr/lib64/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7ff01e9748e2] -> /usr/lib64/dovecot/libdovecot.so.0(+0x73d91) [0x7ff01e96ed91] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7ff01e997653] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7ff01e99807d] -> /usr/lib64/dovecot/libdovecot.so.0(messag...
2016 Mar 30
2
crash after out of memory?
...ent+0x118) [0x7fb0b82a96a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc00ba) [0x7fb0b85e10ba] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb0b82a991d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7fb0b828d2a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x6e919) [0x7fb0b8287919] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb0b82a991d] -> /usr/lib/dovecot/libdovecot.so.0(message_pars...
2005 Jun 16
1
imap crash
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] == '\n' || (gdb) bt full #0 0x08094e5c in message_parse_header_next (ctx=0x80c8e10, hdr_r=0xbffff64c) at message-parser.c:755 msg = (const unsigned char *) 0x0...
2008 Oct 23
4
Possible header parsing problem
...Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii <br><font size=2 face="sans-serif">blah blah blah in HTML</font> --=_alternative 006F3A73872574E8_=-- I did a little bit of tracing through the parsing code (message-header-parser.c:message_parse_header_next()) and it appeared that the boundary in the Content-Type header was not parsed correctly, evidently because the header line was folded in the middle of the boundary string. RFC 822 appears to allow folding in a quoted string like this (?3.3 "quoted-string"), so I'm curious whether...
2010 Dec 21
2
over quota issue
...vecot.so.0(i_stream_seek+0x68) [0xe6cb68] -> /usr/local/lib/dovecot/libdovecot.so.0 [0xe6fda8] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x7a) [0xe6cc3a] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x2b) [0xe6ceab] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x87) [0xe504a7] -> /usr/local/lib/dovecot/libdovecot.so.0 [0xe51d5e] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x43) [0xe51543] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parser_parse_header+0x2f) [0xe5175f] -> /usr/local/lib/dovecot/libdovecot-st...
2005 Nov 15
0
process imap SIGSEGVs when getting STATUS on mbox box
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 if (msg[0] == '\n' || (gdb) bac #0 0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759 #1 0x00000000004297bb in mbox_sync_parse_next_mail (inpu...
2016 Aug 19
2
Crash on opening mailbox
...am_read_data (stream=0x7d52a0, data_r=data_r at entry=0x7ffc6c9df6d8, size_r=size_r at entry=0x7ffc6c9df6e0, threshold=threshold at entry=1) at istream.c:563 ret = <optimized out> read_more = false __FUNCTION__ = "i_stream_read_data" #15 0x00007f328d303042 in message_parse_header_next (ctx=0x7e2ee0, hdr_r=hdr_r at entry=0x7ffc6c9df780) at message-header-parser.c:84 line = 0x7e2ee0 msg = 0x7dd2f2 "XQgc2UgbWFwb3ZhdCBha3R1YWxuaSBwb2tyeXRpIHNpZ25hbHUgbmVtYSBzbXlzbCwg\namVkbmFrIHNlIHN0YWxlIG1lbmkgYQpwb3RyZWJuYSBkYXRhIG8gbmFzdGF2ZW5pIHZ5a29udSBh\nIHNtZXJvdmFuaSBhb...
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
2019 May 24
2
Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
...f9) [0x7fbc52b84af9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x7a) [0x7fbc52bb531a] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x2f) [0x7fbc52bb565f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d)[0x7fbc52bb604d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68)[0x7fbc52b8b3f8] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x52)[0x7fbc52b8bdd2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcadae) [0x7fbc52f26dae] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcc0ac) [0x7fbc52f280ac] -> /usr/lib/dovecot/libdovecot-storage.so.0(...
2008 Dec 02
1
Panic 1.1.x
...fatal_finish (type=<value optimized out>, status=0) at failures.c:150 backtrace = 0x80f28b0 "imap [0x80c4510] -> imap [0x80c456a] -> imap [0x80c3e6c] -> imap [0x80ca8a4] -> imap(i_stream_read+0x2d) [0x80c893d] -> imap(i_stream_read_data+0x1d) [0x80c8a4d] -> imap(message_parse_header_next+0x7c"... #4 0x080c456a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80d7dcc "file %s: line %d (%s): assertion failed: (%s)", args=0xbfa4e634 "Cw\016\bT") at failures.c:430 No locals. #5 0x080c3e6c in i_panic (format=0x80d7dcc "file %s: line %...
2010 Mar 29
3
2.0.beta4, Panic: stream doesn't support seeking backwards
...ib/dovecot/libdovecot.so.0(i_stream_seek+0xbb) [0xb76be1db] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c08a9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x40) [0xb76be570] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x6d) [0xb76a7b6d] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4302] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a498f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a3f61] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4072]...
2008 Oct 09
5
Panic 1.1.4
...of || stream->istream.stream_errno != 0) Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Raw backtrace: imap [0x80c3a30] -> imap [0x80c3a8a] -> imap [0x80c338c] -> imap [0x80c9d04] -> imap(i_stream_ read+0x28) [0x80c7e28] -> imap(i_stream_read_data+0x1d) [0x80c7edd] -> imap(message_parse_header_next+0x7c) [0x80bbcdc] -> imap [0x80b9385] -> imap [0x80b9aa7 ] -> imap [0x80b9bb4] -> imap [0x80b9c95] -> imap(i_stream_seek+0x69) [0x80c7db9] -> imap [0x8071763] -> /usr/lib/dovecot/imap/lib20_mail_log_plugin.so [0xb7f a3aec] -> /usr/lib/dovecot/imap/lib20_mail_log_plugin.so...
2010 Dec 20
1
quota issues
...vecot.so.0(i_stream_seek+0x68) [0x78bb68] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x78eda8] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x7a) [0x78bc3a] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x2b) [0x78beab] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x87) [0x76f4a7] -> /usr/local/lib/dovecot/libdovecot.so.0 [0x770d5e] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x43) [0x770543] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parser_parse_header+0x2f) [0x77075f] -> /usr/local/lib/dovecot/libdovecot-st...
2010 Aug 08
1
Dovecot 2.0.rc4 core dumped with Alpine 2.00
...ecot/libdovecot-storage.so.0(+0x60520) [0x1ef520] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read+0x77) [0xa47967] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3e) [0xa47c8e] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x78) [0xa2eb08] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x2472a) [0xa3072a] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x32) [0xa2fc82] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_header+0...
2019 Mar 25
2
v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)
...l_parse_header+0xfe) [0x7f170b47422e] -> /usr/lib/dovecot/libdovecot.so.0(+0x7979f) [0x7f170b11979f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7f170b1437e3] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f170b14422d] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x72) [0x7f170b11f3d2] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7f170b11fd7f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_headers_get_envelope+0x138) [0x7f170b475448] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_special+0x1a1) [0x7f170b4796...
2008 Jul 07
2
Possible bug in v1.1.1
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
2018 Mar 03
2
pigeonhole 0.4.22 with sieve_before script crashes
...e88c] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8c0155294d] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x2c8) [0x7f8c015c99d8] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f8c015ca15d] -> /usr/local/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x63) [0x7f8c015a72e3] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x7efb1) [0x7f8c015a0fb1] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7f8c015c9763] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f8c015ca15d] -> /usr/local/lib/dovecot...