similar to: dsync: Invalid mailbox first_recent_uid

Recently we changed Postfix to use Dovecot for our SASL authentication and we ran into trouble with some of our clients having extraneous spaces at the end of their usernames. The quick fix was to add a space to username_chars. The slightly longer fix was a pretty simple patch to Dovecot. I put the trimming in auth_request_fix_username. I didn't think it warranted a full strfuncs

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the

Currently running 1.0.2 with 1.1b1 listening on a different port. On first pop3 login on 1.1b1 I received an immediate disconnect (I was testing with telnet) with the log entries below. Subsequent logins work fine. Other accounts that I tried did not have the same problem. So this is probably isolated to some bad indexes or something, but I thought I should let Timo know. Regards, David Here

Hi, I get core dumps, probably during dsync: Core was generated by `dovecot/imap postlogin'. Program terminated with signal 6, Aborted. [New process 7727] #0 0x00002ba911c04ed5 in raise () from /lib/libc.so.6 #0 0x00002ba911c04ed5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00002ba911c063f3 in abort () from /lib/libc.so.6 No symbol table info available. #2

Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file

Core was generated by `dovecot/indexer-worker'. Program terminated with signal 11, Segmentation fault. #0 0x00007f30f7ad056d in __exchange_and_add (__val=-1, __mem=0xfffffffffffffff8) at /usr/src/debug/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/atomicity.h:49 49 { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } (gdb) bt full #0

I'm really sorry, but it was a long day yesterday. I forgot to mention that I used alpine:edge (based on the alpine master branch) image to set up the build environment. So there were some version changes. dovecot --version: 2.3.3 (dcead646b) apk info musl: musl-1.1.20-r2 description: the musl c library (libc) implementation Configuration was unchanged wrt to my first mail. Maybe it's

On 21.12.2018 15.01, Tim Mohlmann via dovecot wrote: > Hi, I now this is kinda impolite to ask, but I would like some feedback > on this issue. I'm representing the Mailu user group here, plus the fact > that my own production server is affected and starts to crash due to > file corruption as a result of the indexer-worker segfaults. Last night > my server became unavailable

Hi, I've just enabled FTS via Lucene on my Dovecot 2.2.24 installation but I see the indexer crashing ?always?. This simple testcase with a very tiny testing mailbox exposes the issue immediately: doveadm -v index -u anmesse INBOX Program received signal SIGSEGV, Segmentation fault. rescan_clear_unseen_mailbox (rescan_ctx=rescan_ctx at entry=0x0, vname=0x555555839820 "INBOX.Testfolder

Hi, i tried to setup replication since some days but I'am stuck now. My conf: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.3.1.el6.x86_64 x86_64 CentOS release 6.5 (Final) dsync_remote_cmd = ssh -l%{login} %{host} /usr/bin/doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} log_path = /var/log/dovecot mail_gid = 5000 mail_home = /var/vmail/%d/%n mail_location =

Hi, I have a mailbox where indexing fails with the following error: # /opt/dovecot2/bin/doveadm -c /tmp/dovecot.conf -o mail_location=/tmp/skesselring index '*' doveadm(root): Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) doveadm(root): Error: Raw backtrace:

Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further inspection Full

Hi all I''ve upgraded the rails plugin from 0.7.5 to 0.7.5.1 (plugin/remove rspec_on_rails followed by : ruby script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_5_1/rspec_on_rails/vendor/plugins/rspec_on_rails I''ve also updated the rspec gem and removed the older version. I''m running rubygems 0.9.1 on a windows box however, when I try to run a spec

I installed 0.7.5 and the corresponding Rails plugin. Now it seems that the rake command is: rake spec:autotest I immediately ran into several problems: 1. rspec_autotest.rb line 30 has curly quotes and makes Ruby choke 2. Same line, rails_spec is spelled solid, when it should have the underscore But fixing these didn''t get me back going. Now I have to have a rails_spec_server

Hello, We have recently implemented dovecot directors to resolve an ongoing NFS lock/corruption issue. Everything was working great! So we updated our servers from centos 7.3 to 7.7 and dovecot 2.2.10 to 2.3.8 This was a bit of a failure and we were getting spammed with corrupt index files and logs. After we clear the index files with rm rf/mail/d/e/username/Maildir/dovecot*, they just come back

On 10/05/2015 5:47 PM, Timo Sirainen wrote: >> How do I go about debugging this further? How do I go about >> getting a backtrace on what is essentially a child process that >> doesn't produce a core? (Note that my installation normally does >> produce cores when it crashes, so there's something different about >> these indexer processes..) > > One

I've managed to re-compile the alpine packages inside the container, creating the debug symbols and disabling compile time optimizations, as they also disturbed the backtrace. The following output looks much more meaningful. But unfortunately there are still some symbols missing for lucene-core. Let me know if this is enough to work with. (It doesn't seem to be musl after all?) Reading

On 10 May 2015, at 06:19, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > > I'm now seeing these crashes in the indexing code: > > May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1 (3903badc4ee0+) starting up for imap, lmtp, sieve > ... > May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker disconnected, discarding 1

Log: Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): /home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216 -> 2) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap [0x80efdb1]