[Tickets #9845] Re: Error displayed and logged whenever a message is deleted or restored

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9845
------------------------------------------------------------------------------
  Ticket             | 9845
  Updated By         | jcblanco at fi.upm.es
  Summary            | Error displayed and logged whenever a message is
                     | deleted or restored
  Queue              | IMP
  Version            | 5.0
  Type               | Bug
  State              | Feedback
  Priority           | 3. High
  Milestone          |
  Patch              | 1
  Owners             | Michael Slusarz
+New Attachment     | imap.log.txt
------------------------------------------------------------------------------


jcblanco at fi.upm.es (2011-04-08 19:11) wrote:

>> It sort of sounds like your IMAP server is broken.  The only way this
>> could happen is if your server sent MODSEQ information even if no
>> CONDSTORE enabling command has been sent.
>
> Well is a typical dovecot 1.2.9 installation, and i'm not the only  
> one giving this error, if you see the distribution list there is  
> another person with the same problem.
>
>>
>> I will commit the patch since it doesn't add much overhead and will
>> cover the situation I describe above.
>>
>> For my personal information, could you provide an IMAP log of a
>> mailbox SELECT/EXAMINE so I can verify this?  Details on how to get
>> IMAP debug log is below
>
> I'll try but I've never done so.

There is a LOG I don't know if it has all you need but I've done the  
same steps that produce the error.

Regards
>
>>
>> -----
>>
>> To further debug this issue, we need details of the IMP -> IMAP/POP
>> communication.
>>
>> To enable debugging, see instructions contained in
>> imp/config/backends.php (the 'debug' config parameter).
>>
>> Debugging should not be enabled on a production server,   Attach/post
>> only the portion of the log that directly deals with the problem
>> reported (it may be simplest to clear the log file and then perform
>> the event that causes the error).
>