similar to: 1.1b16: (buffer_set_used_size): assertion failed: (used_size <= buf->alloc)

This is log from dovecot 2.2.10: 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Error: Corrupted transaction log file /pracmail/domain/user/mail/.sent-mail/dovecot.index.log seq 16777216: log file shrank (868 < 6144) (sync_offset=6144) 2014-01-11T09:55:14+01:00 server/a.b.c.d dovecot: imap(user at domain): Panic: file buffer.c: line 307 (buffer_set_used_size):

Hi, We have a crash in dovecot 2.2.7 2013-12-11 10:38:44 imap(xxx at example.com): Panic: file buffer.c: line 307 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) 2013-12-11 10:38:44 imap(xxx at example.com): Error: Raw backtrace: /opt/dovecot- 2.2.7/lib/dovecot/libdovecot.so.0(+0x672a2) [0x7f576b9742a2] -> /opt/dovecot- 2.2.7/lib/dovecot/libdovecot.so.0(+0x67306)

dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I. -Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox -DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a imaptest.c: In client_append function: imaptest.c:1492: error: too many arguments for i_stream_create_limit function

I have a script that is attempting to notify a user that a job has finished. However, when called from within the script nothing is received by the user. When the equivalent message is sent from the command line, the user receives the message. The portion of the script that is relevant is below: ----- cut from script ----- #!/usr/bin/sh : : MESSAGE="$WINNAME, your job $_3GJOB\nhas

Hi all, I am trying to reproduce rails 3.2 behaviour with fields_for and nested attributes. class ControllerAction < ActiveRecord::Base has_many :interactions, dependent: :destroy has_many :roles, through: :interactions scope :controllers, lambda {|name| where("controller_name_id = ?", name)} scope :actions, lambda {|name| where("action_name_id =

Hello I''m hoping you guys can help me figure this out. When I use shorewall clear my windows openvpn client connects perfectly every time. But when I have the shorewall up 90% (not every time) it will connect for about a second and then the connection will reset and that will repeat over and over so i never don''t really get a steady connection at all. I can tell you that

Hi, configure option "--disable-ipv6" does not work for me in version 1.1.beta16 (and earlier versions). The following patch fixed this problem for me. Heiko ============================================================ --- configure.in.org 2008-02-16 15:35:53.000000000 +0100 +++ configure.in 2008-02-17 01:30:21.675931789 +0100 @@ -23,8 +23,8 @@ AC_ARG_ENABLE(ipv6, [ --enable-ipv6

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

I have a script that is attempting to notify a user that a job has finished however, when called from within the script nothing is received by the user. ----- cut from script ----- #!/usr/bin/sh : : MESSAGE="$WINNAME, your job $_3GJOB\nhas successfully completed" echo "$MESSAGE" | /path/to/smbclient -M trout > /dev/null 2>&1 echo

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

Dear All, I think I've hit a bug after migrating our mail server to the newest version of dovecot (version 2.2.15). When I try to list all imap folders for one user the imap process crashes. The listing to a specific folder (ex. INBOX) works fine, only the "*" crashes. Client side: --------------------- [root at mb log]# telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to

For quite some time I have seen dovecot imap exit with a sig11 without any other error message, but usually with the frequency of between once per week and once per day (per server). A few weeks ago I finally enabled core dumping with debug symbols and it seemed to happen less often. I finally caught a coredump that wasn't overwritten. I have no idea what on the client end may cause it,

http://dovecot.org/test/ - Fixed dying with SIGIO signal with busy Maildir + Linux + IDLE system - Fixed maildir syncing: "UIDs not ordered in file" errors could have occured sometimes wrongly - --with-ioloop=epoll enables epoll code with Linux 2.6. Untested after my changes. - Pretty big changes in internal index handling code (I started this change 2-3 months ago..) Keywords are

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

We are working on migrating Dovecot 1.2.17 running on AIX 5.3 (believe it or not!) to Dovecot 2.0.13 running on Ubuntu. We have hundreds of users mboxes we will be migrating. My question is regarding the index files. Should we remove those after the migration, but before we open it up to users so Dovecot can create new ones? I did a test migration of a single user, and Dovecot detects the

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz.sig If all goes well, I'll release v1.1.rc1 in a couple of days. Now's a good time to start testing v1.1 :) Changes since beta15: - Squat is finally working and supports expunging messages from it. I've been stress testing it and can't find any problems

Hello, I am trying to use Xen Enterprise (its free version). Until now I have no problem, but now I want to create a new virtual machine based in debian etch, not debian sarge (the debian version included in xen templates). So I am looking for a way to create my own template, but I haven''t found any documentation about that. Looking the files, I have found that templates are stored in

This patch series allows user-specified mount commands to be sent in via kernel command line ("kinit_mount=...") or via an embedded /etc/fstab file. The first patch is a cleanup of a patch sent last November by San Mehat (http://web.archiveorange.com/archive/v/EazJNBMORV2U7E0coh5h); the next two are small improvements or bug fixes.