search for: parse_next_body_to_boundari

Displaying 7 results from an estimated 7 matches for "parse_next_body_to_boundari".

2007 Oct 21
1
Problem with fts found against Dovecot hg; examples + trace attached
I've been wanting to try out Squat for full-text indexing for a while now, so I finally gave it a whirl. I did a fresh pull from hg. I have it enabled, but it's taking *forever* to do a query. (Using alpine, I issued a Select command for all messages with some word anywhere, which presumably caused the Squat indexer to run.) I think Dovecot is infinite looping. I thought something
2010 Sep 15
1
imap processing spinning on the CPU
Version: 2.0.2 OS: Mac OS X 10.5.8 IMAP Client: Apple Mail.app on 10.5.8 Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get. I know of one other person who is seeing this on a FreeBSD server (that person moved back to dovecot 1.2 which 'solved' the problem there). I didn't notice anything in the list archive
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
2010 Sep 17
1
fts_squat hanging on some messages
Hello, I recently upgraded to dovecot 2.0.2 (on gentoo ~amd64) and now fts_squat's index building seems to hang for some of my mailboxes. The imap process gets stuck at 100% cpu usage and dovecot.index.search is never touched. I traced the problem to a message (attached) for one of the problematic mailboxes. Also attached are a full backtrace and the output of dovecot -n. The problem
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
2010 Aug 10
1
Why p_strdup and other string functions uses loops instead strlen? (dovecot 2.0.rc4)
I did Dovecot profiling on huge e-mail system, and p_strdup was very high on list. I do minor change: p_strdup: /* for (len = 0; (str)[len] != '\0'; ) len++; len++; */ len = strlen(str) + 1; p_strndup: /* len = 0; while (len < max_chars && ((const char *) str)[len] != '\0') len++; */ len = strnlen(str, max_chars); And after changes strdup drop down on the
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"