[Tickets #1819] NEW: IMP message indexes problems

[bugs at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=1819
-----------------------------------------------------------------------
 Ticket             | 1819
 Created By         | kevin_myer at iu13.org
 Summary            | IMP message indexes problems
 Queue              | IMP
 Version            | 4.0.3
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-04-19 07:33) wrote:

Web server - latest version of Tier 1 Horde components (Horde, IMP, Turba,
Ingo, Mnemo, Nag)
Red Hat Enterprise Linux 3 with latest errata

Mail server - Cyrus IMAP 2.1.18, using IMAP with TLS (although problem
occurs with plaintext as well)

After using IMP for awhile, message indexes start to behave erraticly. 
There are two types of problems:

1)  "Requested message not found" when clicking on a message
2)  Clicking on a folder or a link to a previous set of messages takes you
to the wrong folder

Situation #1 seems to be exacerbated when you are reading messages and when
new mail arrives, although it is not limited to this situation.  A fairly
reproducible situation (although not always) is to do the following:

1) Login to Horde/IMP (we are using LDAP authentication, and our IMAP server
uses saslauthd with passthrough to the same LDAP directory server)
2)  Read a message in your INBOX
3)  Do a search for messages that returns a few pages of results.
4)  Return to the INBOX and choose a message
5)  "Requested message not found" is returned and you're dropped back into
the search results page, instead of the INBOX page.

Today, I'm not seeing the "Requested message not found" message as much but
I am getting dropped into the wrong folder when switching between folders,
on a somewhat frequent basis.

While POP access is available to our mail server, there is no POP activity
on my account.

I have done packet captures for non-TLS IMAP connections as well.  When the
"Requested message not found" message is kicked up by IMP, there is zero
IMAP connection traffic, so its not as if the IMAP server is returning an
error.

Perhaps totally unrelated but worth noting is that the occurrence of the
wrong folder being returned is worsened when using an IMAP proxy running on
the web server.  I am not currently using that setup in production, for that
reason, but I can do tests on a test site if needed.

I am using Thread mode, but I see the "Requested message not found" error in
other sorting modes as well.