Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

Hi Jake, thanks for fixing this. I have installed now the newly built package on my production system and will report, if any more core dumps occur. Regards, Andreas Am 31.08.2016 um 20:19 schrieb Jake Goerzen: > Hi Andreas & Timo, > > > I've found out what is causing the incorrect hash in

Use of obox2 and AWS S3

Hi Has anyone used or is using dovecot obox and S3 storage? I see very little chatter or documentation on it. Interested in how mature it is and technical items such as high availability and region replication. I'm guessing that multiple updates to a S3 mailbox is mitigated via the standard

Re: Dsync config help

I was able to workaround the “Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don’t support credentials lookups (to see if user is proxied, because doveadm_port is set)” problem:  => I simply disabled “doveadm_port” and added the port number at the end of the remote URL in

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

Hi Andreas & Timo, I've found out what is causing the incorrect hash in the built packages. Our build system use here at OpenCSW has internal git patching capability. I disabled it and rebuild again. This time all architectures and memory model's are reporting the correct git-commit

dovecot and ldap with problem on userdb

Hi, I have setup a new ubuntu on 16.04.. I have already a running system on 14.04 but wanted to migrate. I get an error when checking user in ldap. +++ Aug 31 18:14:16 auth: Error: ldap_bind Aug 31 18:14:16 auth: Error: ldap_simple_bind Aug 31 18:14:16 auth: Error: ldap_sasl_bind Aug 31 18:14:16

RE: autoexpunge clarification

Thanks Philon, I did read the extra bullets, as indicated in my email below. But your "When the user quits and thus closes his mailbox/connection" is more clear than "after the client is already disconnected", since the latter is really anytime, rather than at the time they quit. I can guess

Re: 2.2.25 dumps core with "Panic: file imap-client.c: line 837 (client_check_command_hangs): assertion failed: (client->io != NULL)"

Hello Timo, from the maintainer of the OpenCSW package I got the below answer. As the newly build package yields another different commit hash (which I cannot find on GitHub too), I would ask, if you are sure that the commit hash-output in 'doveconf -n' is generated correctly? The headline of

Re: autoexpunge clarification

Hi Micheal, the article is fine if you continue reading it to the next bullet points about IMAP, POP3 and LMTP. In short words… When the user quits and thus closes his mailbox/connection, Dovecot quickly looks through the folders to clean up mails which are older then configured days. In the

Re: ACL List uses wrong namespace for permissions

On 26.04.2016 18:03, Harald Leithner wrote: > Hi, > > I'm using dovecot 2.2.devel (11c704a) with lazyexpunge and shared > Mailboxes, this seams to work since the latest patch. > > There is only one problem creating the correct dovecot-acl-list, if I > login as the normal user that has set

Re: Panic on cleanup

On 12.07.2016 22:25, Harald Leithner wrote: > Hi, > > I got a doveadm panic while running purge -A with 2.2.25 > > > doveadm(x...@itronic.at): Panic: file mdbox-map.c: line 1359: unreached > doveadm(x...@itronic.at): Error: Raw backtrace: > /usr/lib/dovecot/libdovecot.so.0(+0x8dc6e)