[Tickets #6623] Message cache update flags cannot handle imap ranges
bugs at horde.org
bugs at horde.org
Fri Apr 18 12:36:10 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/6623
-----------------------------------------------------------------------
Ticket | 6623
Created By | janne.peltonen at helsinki.fi
Summary | Message cache update flags cannot handle imap ranges
Queue | IMP
Version | 4.2-RC3
Type | Bug
State | Unconfirmed
Priority | 2. Medium
Milestone |
Patch |
Owners |
+New Attachment | handle_imap_range_in_flag_cache.patch
-----------------------------------------------------------------------
janne.peltonen at helsinki.fi (2008-04-18 08:36) wrote:
"Empty folder" operation gives the list of message indices in the form
understood by the imap protocol to mean "from to first to the end", that
is, "1:*". Everything else in IMP seems to handle this OK, but updateFlags
function in lib/IMAP/MessageCache.php doesn't - it apparently excpects a
list of explicite message id numbers, not a one-membered list that contains
an IMAP range. Result: the messages are flagged as deleted on the server,
but not in cache, so IMP shows them without overstrike in the mailbox
index. (However, "Hide deleted", "Purge deleted" etc. do work.) The
attached patch adds the imap range "1:*" as a special case to the _loadUIDs
argument $uids - if $uids has "1:*" as its first element, we retrieve all
the UIDs we have in cache. I'm not sure whether this actually resolves the
problem; seems to work for me this far...
More information about the bugs
mailing list