210621 - Exchange 5.5 IMAP SEARCH CHARSET ISO-8859-1 error: Invalid AND key in SEARCH command

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: IMAP, defect)

Description

[Oliver Schoett]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

My INBOX resides on Microsoft Exchange IMAP4rev1 server version 5.5.2653.23

Tools / Search Messages... with search string qualität (containing a German
Umlaut character) results in an error pop-up

   Alert

   The current command did not succeed.  The mail server responded:
   Protocol Error: "Invalid AND key in SEARCH command"

for every (sub) folder searched, and no search result.  The relevant extract
from the IMAP log file is below.  There is no error when searching for a string
without the Umlaut Character, and no error when searching (with Umlaut) from the
Quick search bar above the message listing.

(Could well be an Exchange bug.)


Reproducible: Always

Steps to Reproduce:




Excerpt from the IMAP log around the error:

2812[1ec7778]: 1bdb170:mucexch2.muc.sdm.de:S-INBOX:ProcessCurrentURL: entering
2812[1ec7778]: 1bdb170:mucexch2.muc.sdm.de:S-INBOX:SendData: 9 uid SEARCH
CHARSET ISO-8859-1 UNDELETED HEADER SUBJECT "qualität"
2812[1ec7778]: ReadNextLine [stream=207baf0 nb=0 needmore=1]
2812[1ec7778]: ReadNextLine [stream=207baf0 nb=59 needmore=0]
2812[1ec7778]: 1bdb170:mucexch2.muc.sdm.de:S-INBOX:CreateNewLineFromSocket: 9
BAD Protocol Error: "Invalid AND key in SEARCH command"
0[273ef8]: 145d440:mucexch2.muc.sdm.de:NA:SetupWithUrl: clearing
IMAP_CONNECTION_IS_OPEN

Comment 1

[Oliver Schoett]

In contrast, here are the IMAP SEARCH commands from Tools / Search Messages...
where the search string contains only ASCII characters (and the search works as
expected):

2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:ProcessCurrentURL: entering
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:SendData: 10 uid SEARCH
UNDELETED HEADER SUBJECT "qualitaet"
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=0 needmore=1]
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=10 needmore=0]
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:CreateNewLineFromSocket: * SEARCH
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=25 needmore=0]
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:CreateNewLineFromSocket: 10
OK SEARCH completed.
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:ProcessCurrentURL: entering
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:SendData: 11 uid SEARCH
UNDELETED HEADER SUBJECT "ae"
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=0 needmore=1]
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=64 needmore=0]
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:CreateNewLineFromSocket: *
SEARCH 19912 20900 21106 21452 21854 21855 21859 21860 21862
2648[1d31c18]: ReadNextLine [stream=1eeecc0 nb=25 needmore=0]
2648[1d31c18]: 1c22498:mucexch3.muc.sdm.de:S-INBOX:CreateNewLineFromSocket: 11
OK SEARCH completed.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.