Tickets :: Comment on [#13144] IMAP error QRESYNC not enabled/invalid parameters

* Your Email Address
* Spam protection	Enter the letters below: .__ . .. .. .. . \| \\| \|\|\/\|\| \|\ / \|__/\|/\\|\| \|\|/\\| \/
Comment	> imapproxy is terrible when it comes to handling the instance > where it's connection to the backend is broken. From the client > perspective, it is impossible to know that the underlying connection > has been destroyed. > > Horde/IMP tries to cache connection details when using imapproxy so > we don't have to send the same commands over and over again. If > imapproxy doesn't report the error from the underlying server, Horde > doesn't know that it has to clear its internal IMAP state cache. > > There's really no reason to be using imapproxy anymore these days > though for performance reasons, at least if using Dovecot 2+. > > (Clearing the IMAP cache actually doesn't have much to do with this. > All you are doing is preventing QRESYNC from being used in that > initial connection, until the cache is primed again. It's not fixing > the underlying imapproxy issue). > > In short, either stop using imapproxy or add XIMAPPROXY to the list > of ignored capabilities in backends.php. Or simply accept this > imapproxy issue if it is extremely rare on your systems.
Attachment
Watch this ticket