[Tickets #8287] Re: POP3 - Can't see content of a mail (bad mail is displayed)

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/8287
------------------------------------------------------------------------------
  Ticket             | 8287
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | POP3 - Can't see content of a mail (bad mail is
                     | displayed)
  Queue              | IMP
  Version            | 4.3.4
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-06-25 17:31) wrote:

>> I can't reproduce.  Sounds like a c-client issue.
>
> The problem is caused by a bug within the cache mechanism. C-client  
> works well, since the displayed source code of a message is OK. If  
> the following configuration is used:
>    $conf['cache']['driver'] = 'sql';
> and the attachments are not displayed in a invalid way, it is  
> sufficient to delete all the entries in horde_cache table and  
> re-login the user. Then, all the attachements correspond with the  
> emails = are displayed where should be.
>
> I guess the bug appears as soon as some mails are deleted from  
> mailbox - maybe it is caused by the mismatch with indexes?

It definitely sounds like a c-client issue.  Sounds like the UIDs  
returned by c-client aren't unique.  The UIDL command is optional in  
POP3 servers - if not present, it is possible c-client is using  
straight message numbers instead.  Not much we can do there since we  
have no way of determining through the c-client API whether UIDL is  
available.

In IMP 5, I have disabled caching entirely for POP3 (as well as  
searching and sorting), albeit for performance and maintenance reasons  
rather than buggy UIDs.  I am wondering if I should entirely disable  
caching in FW_3 too.  I am instead leaning more to a strongly worded  
warning in the config files.