Outlook 2007 Archives

So I am a huge fan of these odd ball issues. When one of my users called me telling me they couldn’t send a “few” messages to people I told the helpdesk I was going to look into it myself.

They got this NDR back:

“None of your e-mail accounts could send to this recipient.”

Now I have never seen that error before, and what really got my interest was there was no x.x.x error code. This lead me to think it was a local issue with the client.

Some Google searching lead me to think it had to do with missing message connectors (like fax, etc..) but this user didn’t have any of that.

Some times it really helps to just talk to the end user. After speaking to her we discovered this only happened when clicking a mailto: hyperlink from a forwarded email down in the thread.

When I went back to my desk I noticed that my FROM: tags were not hyperlinked like the ones from my user.

After comparing the differences I finally noticed that she had the SalesForce.com plug-in installed. What it is doing is actually sending outlook a email type of “MAILTO” instead of SMTP.

After pressing ALT+K you can double click the resolved address and see what the email type is. If its set to MAILTO it will not work. You can however press the internet type button and it will change it to SMTP (which will allow it to send).

So there is no real solution right now, I am going to check with SF.com enterprise support but I have a feeling they wont do anything about it. After showing the end user what not to do and showing how to correct it she was happy enough with the solution.

If you find the same problem or any other add-on causing this please let me know so I can add it to the list.

UPDATE: Thanks to Andrew down there in the comments Outlook 2007 has been patched by MS: http://support.microsoft.com/kb/2475888/en-us

UPDATE 2: Thanks to Tom, we now know MS is hopefully rolling out a patch for Outlook 2010 sometime this month (fingers crossed).

UPDATE 3: I just saw there might be a fix for 2010 you can test out this hotfix from MS. If it works let me know in the comments: http://support.microsoft.com/kb/2475888/en-us or possibly http://support.microsoft.com/kb/2597052.

While am a sure there are a ton of reasons Outlook Anywhere will not work, here are the two huge issues we ran into when getting this working.

1) Wild Card Certificates (special handling)

If you are using a wild card certificate, you will need to run the following connect on whatever CAS server you are using:

Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.contoso.com

You can also check what the current settings are by using:

Note: *.contoso.com is replaced with your wildcard certificate name.

Get-OutlookProvider

by changing that setting it will update autodiscovery to set that into the outlook client configuration as shown here:

For more details about wildcards and Outlook Anywhere go here: http://technet.microsoft.com/en-us/library/cc535023.aspx

2) Issues with IIS and Certificate Settings

Everyone who is trying to get Outlook Anywhere working should triple check that on the root of the IIS site is set to ignore client certificates.

To do that first go to the properties of the IIS website that has your RPC proxy (the root of the website)

Then click the directory Security Tab, and click Edit on Secure communications

Make sure “Ignore Client Certificates” is selected.

You can change all of the sub folders but you must make sure it is set to ignore on the root site.

So there you have it, those were to two issues we had and were able to resolve.

I would like to thank Jason B (one of my Network Administrators) who did the research to discover the second issue.

Tag: Outlook 2007

Fix: None of your e-mail accounts could send to this recipient.

Cannot connect to Outlook Anywhere (Outlook 2007 RPC over HTTP)