6.0.0-alpha12
6/12/25

[#7396] message not found error when message arives after users is logged to imp
Summary message not found error when message arives after users is logged to imp
Queue IMP
Queue Version 4.3
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester dakarin (at) go2 (dot) pl
Created 09/25/2008 (6104 days ago)
Due 09/25/2008 (6104 days ago)
Updated 11/06/2008 (6062 days ago)
Assigned 10/07/2008 (6092 days ago)
Resolved 11/06/2008 (6062 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/06/2008 02:14:39 AM Chuck Hagenbuch Comment #8
State ⇒ No Feedback
Reply to this comment
Given that no developer can reproduce what's in this ticket, and no 
one can tell us how to do so, I'm closing it. We can reopen it if any 
of that changes.
10/27/2008 08:40:31 AM ovidiu (at) mybox (dot) ro Comment #7 Reply to this comment
After installing a fresh groupware-webmail-1.2 the problem 
disappeared, so I figured it has something to do with the imp 
settings. After playing around with that a little, I managed to 
reproduce it, then made it disappear by erasing imp's settings for my 
account from the database.



I don't know exactly which setting or combination of produces this, 
but I think it's sort order and sort by - I used to sort my messages 
by date, descending.



Hope it helps.
10/26/2008 12:01:41 PM ovidiu (at) mybox (dot) ro Comment #6 Reply to this comment
I have the same issue, but for me it doesn't happen only with new 
messages, but also with older messages - usually the last 4-5 
messages, no matter if they were received before or after login.



1. Clicking one of those messages returns to the folder, with the 
error message.

2. Selecting one or more messages and then clicking "View Messages" 
produces the following error:

"Fatal error: Call to undefined method PEAR_Error::findBody() in 
/srv/www/novit.ro/mail/imp/thread.php on line 99"

3. Deleting doesn't work.



BUT:



Opening an older message and then using the "Next Message/Prev 
Message" links works ok. Deleting works too.
10/20/2008 06:40:13 PM Chuck Hagenbuch Comment #5 Reply to this comment
With current HEAD, I am seeing very unpredictable behavior in IMP (not 
DIMP) when deleting messages (with the preference to automatically 
move to the next message). This is not true in current FW_3. It 
doesn't seem to be related to new mail; at least at one point I was 
getting "Requested message not found" any time I tried a 
delete-and-next action from the message view.
10/19/2008 03:51:22 PM Jan Schneider Comment #4 Reply to this comment
I still don't see this in 4.3.
10/08/2008 09:26:48 PM dakarin (at) go2 (dot) pl Comment #3 Reply to this comment
You can't be using IMP 4.3 if this error exists since 3 month.
It existed in older versions too.






10/07/2008 12:50:50 PM Jan Schneider Comment #2
State ⇒ Feedback
Summary ⇒ message not found error when message arives after users is logged to imp
Reply to this comment
You can't be using IMP 4.3 if this error exists since 3 month.
09/25/2008 08:23:23 PM dakarin (at) go2 (dot) pl Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ messege not found error when message arives after users is logged to imp
Due ⇒ 09/25/2008
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
1. horde + imp (horde webmail edition)

2. exim 4

3. debian 4

4. horde connects to mailbox using imap

5. when user A logs on to horde (imp) he has a list of messeges

6. while user A is logged on, user B sends email message to user A

7. user A refreshes hist incomming mail list

8. user A sees new messege from user B

9 user A clicks on new message title

10. error is displayed "messege of specified id was not found" (note: 
i've translated it from polish)



After user A logs out and logs on again he can access that message. 
error is present since about 3 months.

Saved Queries