search for: block_res

Displaying 12 results from an estimated 12 matches for "block_res".

Did you mean: block_re
2006 Jun 05
3
possible bug in trunk base.rb? BREAK_RE.
Hello All, first post to the list. I just checked out trunk and it broke my tests. Turns out that the BREAK_RE regex found in base.rb is missing the "/m" mode modifier. I am still getting my head around the library so i may be missing something but was that done on purpose? Thanks. jeremy Index: base.rb =================================================================== --- base.rb
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
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
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
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"
2009 Apr 03
2
Implementation of editheaders in dovecot
Hello. I wrote the hook function for deliver. I want to add support of editheaders in the plug-in for dovecot. For this purpose I wrote the function rarules_get_stream. Remover of headrs works properly, but adding does not work. I took Timo Sirainen's advice from http://markmail.org/message/skb6arnll5gaopdr . Do I use a correct way of creation of a message? I give backtrace and a
2023 Mar 12
2
dovecot crash with Panic: file istream-header-filter.c: line 663
Hi - I'm hitting a crash in dovecot, I get this logged followed by a terse stack trace and systemd-coredump details not included here - full gdb stack trace and more details are further down: Mar 12 10:32:26 goffin dovecot[8269]: imap-login: Login: user=<patman>, method=PLAIN, rip=192.168.1.4, lip=192.168.1.1, mpid=8477, TLS, session=<5RvGYLf2RrDAqAEE> Mar 12 10:32:26 goffin
2009 Aug 13
4
Crash in v1.2.3: istream.c: assertion failed on line 99
Hi, I have a couple of people bumping into an issue with their imap process crashing - from the users perspective, their mail client (thunderbird) just stops recieving new mail. It still seems to be possible for them to read their mail using squirell mail. When it crashes, it leaves behind a log message like this on the server: Aug 12 15:52:25 fury dovecot: imap-login: Login:
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
2020 Sep 21
1
AW: doveadm search segfault Dovecot 2.2.22
Hey, i am now a bit deeper into dovecot debugging with gdb and have a full bt now, with debugging infos. Is there a patch that resolve this Problem in dovecot 2.2.22-1ubuntu2.13 for ubuntu 16? Here the bt: (gdb) bt full #0 0x00007ffff73cf3f3 in array_count_i (array=0x555555810d38) at ../../src/lib/array.h:155 No locals. #1 message_part_finish (ctx=ctx at entry=0x555555810ce0)
2010 Sep 01
3
Dovecot - some more optimisations
I did some more optimisation. Most performance hit in Dovecot do "for loop" in string operations. In one case (in message-parser.c) "for loop" has another "for" inside with the same variable used as iterator. This case is very hard to optimise by compiler. I do changes only in top functions listed in oprofile. Maybe I do more in future. Code was analysed and
2008 Feb 20
1
(message_parser_parse_next_block): assertion, failed: (ctx->input->eof)
dovecot 1.1b16 Feb 19 23:32:41 hill dovecot: IMAP(username): Disconnected for inactivity bytes=29831/872 Feb 19 23:32:41 hill dovecot: IMAP(username): file message-parser.c: line 764 (message_parser_parse_next_block): assertion failed: (ctx->input->eof) Feb 19 23:32:41 hill dovecot: child 60831 (imap) killed with signal 6 # gdb /usr/local/libexec/dovecot/imap imap.60831.hill.core GNU