Server: Exchange 2010 sp2
Client: win7 32bit Danish + Office 2010 Danish - Outlook 32bit fully patched and updated (not using cached-mode)

When a user opens a old email, and want to see the rest of the mails in the specific conversation, they either search for the header or use the "related messages" button.

But if the search includes special characters, it wont return a result, even if I know the mail is there and can find it manually

The database in indexed, so that is not the problem.

The searchstring for a conversation in the Danish version of office, is:

[Samtale]:="subject line of the specific email"

Lets say the email they are looking at have a header like this
"Hello my dear MS partner Hlgrenn"

if I run this search: [Samtale]:="Hello my dear MS partner Hlgrenn" I get no result

But if i modify the search to exclude the specuial characters, and remove the [samtale/conversation] like this "Hello my dear MS partner H", then it find the emails

To see if this was a client issue, i troed the OWA and found it worked perfectly. I later tried our Terminal server (win 2008 32bit witn same office installation) and that worked as well. But since that is a server, it's a UK/US OS

So are we stuck at some characterset problem, when using Danish/scandinavian OS versions?

It works in cached mode, but I dont want a +20gb offline file on the client. I want it to work in the live exchange, a

I just ran into this issue, and its by design!

Search in Outlook/Exchange/Windows is just generally broken.

I have just plain given up on this, and search the best I can as I only have outlook to work with.

If I hook up Thunderbird to Exchange (using IMAP), i can do all sorts of "instant search" type things and include any character I want!

If I want to find "$" in the subject, I put "$" in the search, and it works!!

And, it is fast, as it caches the message metadata (but not so fast when searching the entire message body - but at least I can still find messages with a "$" in them...)