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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13144
------------------------------------------------------------------------------
  Ticket             | 13144
  Created By         | maciej.uhlig at us.edu.pl
  Summary            | IMAP error QRESYNC not enabled/invalid parameters
  Queue              | IMP
  Version            | 6.1.7
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


maciej.uhlig at us.edu.pl (2014-04-22 17:19) wrote:

First, let me say I've read tickets #12097 and #12031. Second, I got  
yesterday a series (many) of IMAP errors:

2014-04-22T12:54:01+02:00 host/a.b.c.d horde: [imp] IMAP error  
reported by server. Error in IMAP command SELECT: QRESYNC not enabled  
[pid 27468 on line 570 of "./imp/lib/Imap.php"]
2014-04-22T12:55:23+02:00 host/a.b.c.d horde: [imp] IMAP error  
reported by server. Error in IMAP command EXAMINE: Invalid QRESYNC  
parameters [pid 27022 on line 570 of "./imp/lib/Imap.php"]
2014-04-22T12:56:33+02:00 host/a.b.c.d horde: [imp] IMAP error  
reported by server. Error in IMAP command SELECT: Invalid QRESYNC  
parameters [pid 25372 on line 570 of "./imp/lib/Imap.php"]

The problem was fixed by /usr/bin/horde-clear-cache and the errors  
have (temporarily?) gone. However more interesting is genesis of the  
problem.

Horde connects to dovecot server via imapproxy which told sometime:

2014-04-21T14:50:01+02:00  host/a.b.c.d in.imapproxyd[1795]:  
Raw_Proxy(): IMAP_Read() failed reading from IMAP server on sd [11]:  
Connection reset by peer
2014-04-21T14:50:01+02:00  host/a.b.c.d in.imapproxyd[1795]: LOGIN:  
'user at domain' (127.0.0.1:47602) no previous connection: creating a new  
one
2014-04-21T14:50:01+02:00  host/a.b.c.d in.imapproxyd[1795]: LOGIN:  
'user at domain' (27.0.0.1:47602) on new sd [8]
2014-04-21T14:50:01+02:00 c host/a.b.c.d in.imapproxyd[1795]:  
IMAP_Line_Read(): connection closed prematurely.
2014-04-21T14:50:01+02:00 host/a.b.c.d in.imapproxyd[1795]:  
Raw_Proxy(): Failed to read line from client on socket 16

What about dovecot server? It coredumped with

2014-04-21T14:50:01+02:00 imap/e.f.g.h dovecot: imap(user at domain):  
Fatal: master: service(imap): child 14593 killed with signal 6 (core  
dumped)

Well, we see what has happened: dovecot dumped core, imapproxy  
connection died, Horde signalled IMAP error and... I'd say Horde has  
written damaged data into cache file. Then, subsequent IMAP accesses  
ended with QRESYNC problems until horde-clear-cache was run.

The question is, are you able to prevent writing of corrupted data to  
cache files? And, what I can do to find out what failed next time the  
problem arises?