WinHTTP does not support PAC URLs that use a file:// prefix. In this situation, you can't use Outlook Anywhere to connect through this proxy to an on-premises Exchange 2013 server, an on-premises Exchange 2010 server, or Exchange Online. (We've got three persons of name Sven Fescher listed in GAL, but the LDAP address should be unambiguous, I guess.Assume that you have a proxy that's set up by using a file://-based PAC file.

The other information comes from the Outlook Contact Properties first address fails, the second can be resolved.

The first line of each address gives the LDAP string I can retrieve from the MailItem.Sender property. Here are two sample addresses (I've altered user names and domain name). (We've got three persons of name Sven Fescher listed in GAL, but the LDAP address should be unambiguous, I guess.) The following three questions come up my mind:ġ) How can I resolve 'To:' addresses unambiguously?Ģ) Is it possible to get an array of resolved recipients if the names match more than one recipient?ģ) What's the problem with the first address? The other information comes from the Outlook Contact Properties p=bummelmail o=Exchange s=Fescher2 g=Sven first address fails, the second can be resolved. Using the LDAP address to resolve the recipient fails. So in the Sender property of MailItem, the name of person #1 appears, whereas the LDAP e-mail address of person #2 appears. With one of our e-mails, person #1 sent an e-mail on behalf of person #2. If two users in the GAL share this same name, then the name can not be resolved by Outlook. For the 'To:' addresses I only have the user name available to resolve the recipient.

Outlook 2010 can39t connect to server