similar to: (mail_index_expunge): assertion failed: (!t->view->external) Is this a bug?

Hi all, I was wondering if anyone's seen anything like this? Nov 15 14:16:13 olympic dovecot: imap-login: Login: postmaster [192.168.0.32] Nov 15 14:17:05 olympic dovecot: IMAP(postmaster): file mail-index-transaction.c: line 247 (mail_index_expunge): assertion failed: (!t->view->external) Nov 15 14:17:05 olympic dovecot: child 20184 (imap) killed with signal 6 Nov 15 14:17:19 olympic

Nov 18 17:29:54 gir dovecot: imap-login: Login: jmcvetta [69.106.50.255] Nov 18 17:30:02 gir dovecot: IMAP(jmcvetta): file mail-index-transaction.c: line 247 (mail_index_expunge): assertion failed: (!t->view->external) Nov 18 17:30:02 gir dovecot: child 31094 (imap) killed with signal 6 I saw this in my maillog. I have no idea what that user is doing, but I can harrass him and find out if

I use dovecot-1.1.10 and dovecot-sieve-1.1.6 /usr/local/libexec/dovecot/deliver coredups several times per day with bt like this: (gdb) bt #0 0x0000000800a3a91c in kill () at kill.S:2 #1 0x0000000800a3a88a in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:46 #2 0x0000000800a38f83 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 #3 0x00000000004a7de5 in default_fatal_finish

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, After having moved to using Apple mail.app for offline imap reading (served by a dovecot 1.0-test59 server), I noticed the following in the logs: Feb 14 13:52:48 top dovecot: 3102(schmitta): file mail-transaction-log-view.c: line 86 (mail_transaction_log_view_set): assertion failed: (min_file_seq <= max_file_seq) Is this bad? Would

Hi guys, Anyone know what this error with deliver is (v1.1.1)? 2008-07-03T09:45:19+01:00 mail4 deliver(alexander): Panic: file mail-index-transaction.c: line 642 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) Seen a few of these this morning. Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development *

Hi all. Looking at previous weeks logs I discovered strange errors: "file mail-transaction-log-view.c: assertion failed" dovecot v 1.0.12 Server is hosting more than 500 virtual users. It is compleate dovecot error log; only my own mailbox is affected ...and imap folder affected is "dovecots mailing list" :) While "Corrupted transaction log file" as far as I know

Hi, With 2.4.14 and the ext3 patch on redhat7.2 with my KT133A Athlon system, the kernel panics on boot up just after starting init. I removed the ext3 patch and the kernel did not panic (However I could not mount my ext3 file systems :) ). Is this a proble with ext3 of something different? Thanks for any help. BaRT

BLS #rsync --version rsync version 3.0.4pre2 protocol version 30 Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes rsync comes with ABSOLUTELY NO

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

Hi, I am using dovcot on a Fritz!Box (Linux fritz 2.6.19.2 #1 Fri Apr 18 16:00:34 CEST 2008 mips unknown) And after upgrading from 1.0.9 to 1.0.15 I am getting above assertion, when I do some action like moving or deleting on the IMAP mail box using MailDir on ext2 fs. I use --with-ioloop=epoll and --with-mem-align=4 as build configuration. For dovecof configuration see below details. Thanks

I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108

Hi there, We're running dovecot 2.06, with mdbox. Following message was in our syslog: Jan 20 09:26:48 servername dovecot: [ID 583609 mail.crit] imap(user): Panic: file istream-limit.c: line 79: assertion failed: (v_offset <= lstream->v_size) The problem could be solved on client side, by just deleting the ImapMail-Folder in Thunderbird. Why? Thunderbird tried to move a message, that

Hi, A couple of our important servers, both running FC4 but one i386 and one x86_64, have been crashing recently. They both are running ext3 data=journal with large external journals and high commit intervals. Both machines use the gdth driver for their hardware RAID sets, if that's of any use. I think the hardware is good in both cases. I hope someone finds this data useful enough to be

Yesterday, I upgraded my debian packages from 0.99.14 to 0.99.20050712-2. IMAP service has not been reliable since, and I was seeing crashes with one user. I tried deleting the user's .subscriptions and .imap folders, and forcing the client (Mac OS X's Mail.app) to redownload everything, but that resulted in an empty inbox. Here's what I have: # dpkg -l dovecot*

When trying to start a FreeBSD 9.0 HVM guest I see the following line in qemu-dm-freebsd.log: qemu-dm: /src/xen-stable-hg/src/xen-4.1-testing.hg-build/tools/ioemu-dir/hw/eepro100.c:1320: eepro100_write4: Assertion `!"feature is missing in this emulation: " "unknown longword write"'' failed. The domain crashes. I suspect this occurs because I am trying to build the

I have been getting these assertion failures every couple days, killing the IMAP process. After it happens, I can login immediately and everything is fine until it happens again. Here is the log entry: Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): assertion failed: (view->log_file_offset >=

Hello. I have one account with heavy traffic (big mails) and quite often indexes get corrupted. This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28. When corruption happens lmtp and pop3 segfault on accessing it like: > Mar 27 11:13:50 mbox dovecot[22370]: lmtp(24428): Connect from local

Hi, Would anyone know what these errors mean? Running DoveCot RC15 on RedHat ES 4 Dec 1 17:30:53 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:21 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:25 serv-01 dovecot: pop3-login: file client.c:

On 28 Oct 2016, at 15:36, Gilles Chauvin <gilles.chauvin at univ-rouen.fr> wrote: > > Hello, > > Here is a Panic that happened while doing some testing with two servers both running Dovecot v2.2.26 on CentOS 7. > > These are test servers owning 32 accounts whose data were copied from our production server. > > > What I've done is: > > server01#

Oct 21 10:04:05 alchemy dovecot: imap-login: Login: user=<paulproteus>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS Oct 21 10:05:44 alchemy dovecot: IMAP(paulproteus): file message-decoder.c: line 289 (message_decode_body): assertion failed: (pos < input->size) Oct 21 10:05:44 alchemy dovecot: IMAP(paulproteus): Raw backtrace: imap [0x80c8e10] -> imap [0x80c8d1c] ->