similar to: doveadm index crashes when indexing shared mailboxes

Hi, I've just upgraded our dovecot installation from 1.0.15 to 1.1.13. This went smoothly and just worked -- thank you very much for writing such a high performance and robust piece of software. However, we have a shared mailbox that people can subscribe to. After upgrading to 1.1.13 ... dovecot tries to create a dovecot-acl-list file in the top level of this ... but it creates it

Hello, I have used dovecot to replace an ageing wu-imap installation using the mbox_snarf plugin however I have noticed that when we have more than one client checking the INBOX we then have messages being duplicated in the INBOX. Below is the configuration used as requested in the bug report page. I have confirmed that the duplicates are being caused by dovecot by doing an strace of both

Hi, When I perform a search using doveadm every time it returns different results. For example: $ doveadm search mailbox shared/\* TO stromvers 938ff10527d6be515f5900007b46f991 6 938ff10527d6be515f5900007b46f991 7 938ff10527d6be515f5900007b46f991 8 $ doveadm search mailbox shared/\* TO stromvers 6a8ff10527d6be515f5900007b46f991 1 6a8ff10527d6be515f5900007b46f991 3

Hi, While running doveadm index on a mailbox this gets printed: doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server Error doveadm(neil): Panic: file http-client-request.c: line 792 (http_client_request_send_payload): assertion failed: (ret == 0) doveadm(neil): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x88662) [0x7f0a52750662] ->

Yes, this happens because your SOLR server is reporting 500 Internal Server Error. Aki On 08.11.2016 10:47, W. de Hoog wrote: > Hi, > > While running doveadm index on a mailbox this gets printed: > > doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server > Error > doveadm(neil): Panic: file http-client-request.c: line 792 >

Hi, we are actually deploying a new IMAP-Server, targeting dovecot 2.1.17. Unfortunately, our tests with imaptest did not succeed, were ending in core dumps. We did this test: ./imaptest host=example.com port=143 user=strack pass=secret disconnect_quit no_pipelining mbox=dovecot-crlf That's what we get in dovecot's log: Sep 10 11:17:04 imap-login: Info: Login: user=<strack>,

I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic:

Hi, My end goal is to set up shared mailboxes on a cluster as per: https://wiki.dovecot.org/SharedMailboxes/ClusterSetup I was having very little luck with it, so I had been trying to break down into pieces and get individual components working. So I have things setup on a single server, with a working dovecot instance. I have no director or any thing else running yet, and I am just trying

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:

Hi, We have a Ubuntu 14.04 server with dovecot 2.2.9 If I try to run /usr/bin/doveadm search -u email at exmaple.com mailbox Junk savedbefore 30d It will dump a core file. We have a similar config on an other server and there is no problem there. Any ideas how to prevent the core dump? root at triws2:~# gdb --args doveadm search -u email at example.com mailbox Junk savedbefore 30d Reading

> > Can you do > > p *box $1 = {name = 0x5555557e1f18 "Junk", vname = 0x5555557e1f10 "Junk", storage = 0x5555557e1860, list = 0x5555557e1050, v = { is_readonly = 0x7ffff76e5a50 <fail_mailbox_is_readonly>, enable = 0x7ffff76e5a60 <fail_mailbox_enable>, exists = 0x7ffff76e5a70 <fail_mailbox_exists>, open = 0x7ffff76e5e60

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