6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
10/17/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#10677] Cyrus returning OK when fetching non-existant messages
*
Your Email Address
*
Spam protection
Enter the letters below:
.__.. ..__ .__ .__ [__]|\ || \[__)[__) | || \||__/[__)[__)
Comment
> Guess I am not seeing what the Horde/IMP bug is? > > When parsing FETCH results, we only parse a result if an untagged > response appears (see line 4238 in Client/Socket.php). So in a > conversation like you provided, no fetch responses would be parsed so > we should theoretically be returning an empty array from the fetch() > command. > > Is the issue that IMP is trying to display the message, and we are > relying on an exception to be thrown instead of checking for array > key existence in the return array?
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers