[Tickets #12097] Re: Export of mailfolders fails with cyrus imap

noreply at bugs.horde.org noreply at bugs.horde.org
Thu Mar 7 21:04:14 UTC 2013


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

Ticket URL: http://bugs.horde.org/ticket/12097
------------------------------------------------------------------------------
  Ticket             | 12097
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Export of mailfolders fails with cyrus imap
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.0.4
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-03-07 14:04) wrote:

> You are right it doesn't fix the problem - I traced the bug and  
> found a problem in the method "_updateCache" in class  
> "Horde_Imap_Client_Base".  The mapping array is created unchecked  
> using the getUid() which is either an integer or "null".

We are getting closer.  The problem is that _updateCache() should  
never be called unless we have UIDs.  We can't cache anything with  
sequence numbers, so if UIDs don't exist we shouldn't even reach this  
point.

So it would be great if I could get either a backtrace at the point  
where getUid() returns null (via Horde::debug() - see below) and/or  
the IMAP log of the activity that causes this issue (also see below).



Horde::debug() documentation: http://wiki.horde.org/Doc/Dev/DebugH4





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).





More information about the bugs mailing list