Skip Menu |

This queue is for tickets about the Net-IMAP-Client CPAN distribution.

Report information
The Basics
Id: 85176
Status: open
Priority: 0/
Queue: Net-IMAP-Client

People
Owner: Nobody in particular
Requestors: rob [...] hoelz.ro
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.9501
Fixed in: (no value)



Subject: search method fails to parse some responses correctly
Hello, I'm currently using the search method to check for messages that were received on the current day. Whenever a new message arrives in the current mailbox (or if I manually delete one or more), my mail server (Cyrus Murder) pushes extra data along with the search results (FETCH data with changed flags for deletions, EXISTS + inbox size for additions). The Cyrus developers assured me that these "untagged" responses may be sent after any operation and should be handled correctly. Currently, the search method assumes that the first and only line in the response is a SEARCH response containing the matching ids. With the untagged responses, warnings occur, as well as potential false positive mail IDs (since the count included with EXISTS is interpreted as a mail ID). Please fix this at your earliest convenience. Thanks, Rob
On Fri May 10 06:41:08 2013, hoelzro wrote: Show quoted text
> Hello, > > I'm currently using the search method to check for messages that were > received on the current day. Whenever a new message arrives in the > current mailbox (or if I manually delete one or more), my mail server > (Cyrus Murder) pushes extra data along with the search results (FETCH > data with changed flags for deletions, EXISTS + inbox size for > additions). The Cyrus developers assured me that these "untagged" > responses may be sent after any operation and should be handled > correctly. Currently, the search method assumes that the first and > only line in the response is a SEARCH response containing the matching > ids. With the untagged responses, warnings occur, as well as > potential false positive mail IDs (since the count included with > EXISTS is interpreted as a mail ID). > > Please fix this at your earliest convenience. > > Thanks, > Rob
Thank you for this report. I've applied a patch to fix #84623 that may resolve your issue. Please let me know if there is still a concern, otherwise I will close this.