search for: unhibernation

hello&nbsp; &nbsp; &nbsp;I have some error by LMTP: Mar 09 13:26:42 imap-hibernate(q2 at a.com)<90154&gt;<BqpPNmWg7M9/AAAB&gt;: Error: Failed to unhibernate client: net_connect_unix(/var/run/dovecot/imap-master) failed: Permission denied Mar 09 13:26:42 imap-hibernate(q2 at a.com)<90154&gt;<BqpPNmWg7M9/AAAB&gt;: Info:

...d_finished event's "args" and "human_args" parameters ? were always empty. - mbox: Seeking in zlib and bzip2 compressed input streams didn't work ? correctly. - imap-hibernate: Process crashed when client got destroyed while it was ? attempted to be unhibernated, and the unhibernation fails. - *-login: Proxying may have crashed if SSL handshake to the backend ? failed immediately. This was unlikely to happen in normal operation. - *-login: If TLS handshake to upstream server failed during proxying, ? login process could crash due to invalid memory access. - *-login: v2.3 regress...

...d_finished event's "args" and "human_args" parameters ? were always empty. - mbox: Seeking in zlib and bzip2 compressed input streams didn't work ? correctly. - imap-hibernate: Process crashed when client got destroyed while it was ? attempted to be unhibernated, and the unhibernation fails. - *-login: Proxying may have crashed if SSL handshake to the backend ? failed immediately. This was unlikely to happen in normal operation. - *-login: If TLS handshake to upstream server failed during proxying, ? login process could crash due to invalid memory access. - *-login: v2.3 regress...

...working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2)....

...working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2)....

...OR_SERVER_WRITE_FAILURE error should also be ? treated as "uncertain write failure". - dict-redis: Using quota_clone configured with dict-redis could have ? crashed when Redis responded slowly. - imap-hibernate: Communication trouble with imap-master leads to ? segfault. - imap-hibernate: Unhibernation retrying wasn't working. - imap: Fixed auth lookup privilege problem when imap process was reused ? and user was being un-hibernated. - Fix potential crash when copying/moving mails within the same folder. ? This happened only when there were a lot of fields in dovecot.index.cache. - lib-index:...

...OR_SERVER_WRITE_FAILURE error should also be ? treated as "uncertain write failure". - dict-redis: Using quota_clone configured with dict-redis could have ? crashed when Redis responded slowly. - imap-hibernate: Communication trouble with imap-master leads to ? segfault. - imap-hibernate: Unhibernation retrying wasn't working. - imap: Fixed auth lookup privilege problem when imap process was reused ? and user was being un-hibernated. - Fix potential crash when copying/moving mails within the same folder. ? This happened only when there were a lot of fields in dovecot.index.cache. - lib-index:...

...user at example.org)<5946><wrpbISt2XuUqDF8AAAAAIAAAAAAAABAA>: Debug: acl vfile: file /var/vmail/user/user at example.org//mdbox/mailboxes/INBOX/dbox-Mails/dovecot-acl not found 2018-09-18 23:03:17 imap(user at example.org)<5946><wrpbISt2XuUqDF8AAAAAIAAAAAAAABAA>: Debug: Unhibernation sync: 0 expunges, 1 new messages, 0 flag changes, 1 modseq changes 2018-09-18 23:03:17 imap(user at example.org)<5946><wrpbISt2XuUqDF8AAAAAIAAAAAAAABAA>: Debug: Namespace : Using permissions from /var/vmail/user/user at example.org//mdbox: mode=0700 gid=default 2018-09-18 23:03:17...

...working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2)....

...working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2)....

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with