microsoft.public.exchange.development
[Top] [All Lists]

Re: figure out the language of a user's outlook client

Subject: Re: figure out the language of a user's outlook client
From: "Henning Krause"
Date: Sun, 29 Oct 2006 18:05:47 +0100
Newsgroups: microsoft.public.exchange.development
Hello Stephan,

once you have the url of the mailbox, you can query some properties of the base folder to get the actual urls of the well-known folders.

See http://www.infinitec.de/articles/exchange/getjunkmailfolder.aspx and www.infinitec.de/link.aspx?id=http://msdn.microsoft.com/library/en-us/e2k3/e2k3/_exch2k_getting_well-known_mailbox_folder_urls.asp">http://www.infinitec.de/link.aspx?id=http://msdn.microsoft.com/library/en-us/e2k3/e2k3/_exch2k_getting_well-known_mailbox_folder_urls.asp.

Best regards,
Henning Krause

"Stephan Steiner" <stephan.steiner@xxxxxxxxxxxxx> wrote in message news:u1hfBsZ%23GHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
Hi

I'm using WebDAV to search user's contact folders (send a HTTP SEARCH to exchange-server/exchange/user@domain/Contacts">http://exchange-server/exchange/user@domain/Contacts). This works fine if the user has an English Outlook. The problem is, there are users using a different language Outlook so my search doesn't work for them (in German, the contacts folder would be called Kontakte). Now I'm wondering, is there a means to figure out which folder I should send the search to, without having access to that user's computer (it's a server side application, it performs the search for every user in the domain)? I looked around in the AD and found a field preferredLanguage, but it doesn't appear to match the Outlook language (e.g. I live in the German speaking part of Switzerland and my preferredLanguage is German - correct for all written communication - but I use an English OS and Office). So I'm wondering, is there a way or do I have to force the user to define their outlook language, or even worse send searches to different urls if one comes back 404?

Regards
Stephan



<Prev in Thread] Current Thread [Next in Thread>
Privacy Policy