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