Re: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)

2016-12-06 Thread Aki Tuomi
On 06.12.2016 09:32, Toni Mattila wrote: Hi, On 05-Dec-16 20:28, Toni Mattila wrote: Panicing stopped when all index files where deleted. It happens again in same user account, so rebuilding indexes didn't fix it. Here's bt full instead of just bt: #0 0x001d4402 in __kernel_vsyscall ()

Re: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)

2016-12-06 Thread Aki Tuomi
On 06.12.2016 10:00, Aki Tuomi wrote: On 06.12.2016 09:32, Toni Mattila wrote: Hi, On 05-Dec-16 20:28, Toni Mattila wrote: Panicing stopped when all index files where deleted. It happens again in same user account, so rebuilding indexes didn't fix it. #14 0x08058219 in cmd_search (cmd

Re: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)

2016-12-06 Thread Toni Mattila
Hi, On 06-Dec-16 10:10, Aki Tuomi wrote: Alternatively if you could try and print the args array in cmd_search? f 14 p args[0] p args[1] ... until NULL My hand got sore at first 100 and they are below. I will mail you the binary and core in seperate mail. (gdb) f 14 #14 0x08058219 in cmd_s

Re: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)

2016-12-06 Thread Aki Tuomi
On 06.12.2016 10:44, Toni Mattila wrote: Hi, On 06-Dec-16 10:10, Aki Tuomi wrote: Alternatively if you could try and print the args array in cmd_search? f 14 p args[0] p args[1] ... until NULL My hand got sore at first 100 and they are below. I will mail you the binary and core in seperat

Dovecot: Mails flagged as read get flagged as unread

2016-12-06 Thread plataleas
Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovec

Re: Dovecot: Mails flagged as read get flagged as unread

2016-12-06 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 6 Dec 2016, plataleas wrote: We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is dif

Re: Dovecot: Mails flagged as read get flagged as unread

2016-12-06 Thread plataleas
Hi Steffen Thanks for the reply! - Users are accessing from multiple devices simultaneously - Each user has his own mailbox, we do not use shared mailboxes regards On 12/06/2016 10:14 AM, Steffen Kaiser wrote: > On Tue, 6 Dec 2016, plataleas wrote: > > > We experience some unexpected behavior

Re: 2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)

2016-12-06 Thread Aki Tuomi
On 06.12.2016 10:47, Aki Tuomi wrote: On 06.12.2016 10:44, Toni Mattila wrote: Hi, On 06-Dec-16 10:10, Aki Tuomi wrote: Alternatively if you could try and print the args array in cmd_search? f 14 p args[0] p args[1] ... until NULL My hand got sore at first 100 and they are below. I will

Re: Dovecot: Mails flagged as read get flagged as unread

2016-12-06 Thread Peter Chiochetti
Hi, There is a plugin "mail_log" that you can use to audit what users/user agents are doing, probably mail_log_events flag_change is helpful? -- peter Am 2016-12-06 um 10:24 schrieb plataleas: Hi Steffen Thanks for the reply! - Users are accessing from multiple devices simultaneously - Each

Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0)

2016-12-06 Thread Gilles Chauvin
Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge

Re: Dovecot: Mails flagged as read get flagged as unread

2016-12-06 Thread Alexey Asemov (Alex/AT)
Does this correspond with some index damage in logs? We did have some of these in 2.2.6.0 ("Missing middle file seq=.." followed by reindexing and "lost Recent state" message), with 2.2.7 these seem to have stopped appearing. On 06.12.2016 13:34, Peter Chiochetti wrote: Hi, There is a plugin

Re: v2.2.27 released --- libressl

2016-12-06 Thread Ruga
Results from the application of the following patch from Aki. perl -i -ple 's|^(\s*#include \s*)$|$1\n\t#if OPENSSL_VERSION_NUMBER == 0x2000L\n\t#define OPENSSL_VERSION_NUMBER 0x10001000L\n\t#endif|' configure.ac; compiler-stderr.log Description: Binary data

Segmentation fault in imap_bodystructure_is_plain_7bit

2016-12-06 Thread Mihai Craiu
Hi, I have a lot of errors like this in my log: Fatal: master: service(imap): child 26049 killed with signal 11 (core dumped) Dovecot 2.2.18 build from sources ./configure --prefix=/opt/dovecot2 --with-mysql --with-sqlite --with-solr --with-ssl --disable-rpath --disable-static. Debian Wheezy 3.2.

Setting up replication - First steps...

2016-12-06 Thread SH Development
Just had my first (non-Dovecot) server failure due to dried out caps on the motherboard. Got me to thinking about my single-point-of-failure mail server. Currently running Dovecot and Postfix with no issues, but want to start taking steps just to be safe. I currently run a filesystem backup e

Re: v2.2.27 released --- libressl

2016-12-06 Thread Michael A. Peters
On 12/06/2016 11:35 AM, Ruga wrote: Results from the application of the following patch from Aki. perl -i -ple 's|^(\s*#include \s*)$|$1\n\t#if OPENSSL_VERSION_NUMBER == 0x2000L\n\t#define OPENSSL_VERSION_NUMBER 0x10001000L\n\t#endif|' configure.ac; I use a different method of patching