I work in a hospital with a Win2003 domain, an enterprise CA and Outlook 2003. I also have another remote location that uses an ISP for email. I need to send encrypted emails from my domain location to my remote location. I can send encrypted emails from my remote locale to the domain. All I did was send a signed email from the domain to the remote location added it to Outlook 2007 and added the domain CA into the Trusted Root Authorities. I obtained for my remote local a "Startcom" email cert and sent a signed email to the domain location and added my remote email address to Outlook contacts. But no matter what when I try to encrypt an email to the remote local from the domain location my Outlook 2003 says the certificate for my remote email locale is not usable. What do I need to do to get this to work?

On Wed, 23 Jun 2010 20:05:10 +0000, Myrt Webb wrote: I work in a hospital with a Win2003 domain, an enterprise CA and Outlook 2003. I also have another remote location that uses an ISP for email. I need to send encrypted emails from my domain location to my remote location. I can send encrypted emails from my remote locale to the domain. All I did was send a signed email from the domain to the remote location added it to Outlook 2007 and added the domain CA into the Trusted Root Authorities. I obtained for my remote local a "Startcom" email cert and sent a signed email to the domain location and added my remote email address to Outlook contacts. But no matter what when I try to encrypt an email to the remote local from the domain location my Outlook 2003 says the certificate for my remote email locale is not usable. What do I need to do to get this to work? What is the exact text of the error message? Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca

The small window is titled "Encryption Problems" "Microsoft Office Outlook had problems encrypting this message because the following recipients had missing or invalid certificates or conflicting or unsupported encryption capabilities" Then a text box with the recipients name: "Myrt Webb" Then on the bottom: "Continue will encrypt and send the message but the listed recipients may not be able to read it" The "Continue" button is grayed out.

Hi, The following solutions could be helpful: You receive "Microsoft Office Outlook had problems encrypting this message" when sending an encrypted email to Internet recipient in Outlook 2003 http://support.microsoft.com/kb/555502 You receive the "Microsoft Office Outlook had problems encrypting this message" error message when you address an e-mail message to a LDAP recipient in Outlook 2003 http://support.microsoft.com/kb/870564Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The above do not fit. The contact has a certificate and I am not sending to an LDAP recipient.

The problem has nothing to do with certificates but with Outlook. Outlook cannot find the certificate associated with the recipient because my Contacts are not in an address book. Once I completed the procedure below- it worked! Right-click on Contacts, select properties. On the Outlook Address Book tab, be sure that "Show this folder as an e-mail Address Book". If the option is grayed out, you will need to add an Outlook Address Book to the directories. || Tools, Email Accounts, Add a new directory or address book. Select additional Address Books, Next, Outlook Address Book. Complete the remaining prompts and restart Outlook. repeat the first steps above.

I'm starting to see this exact behavior on multiple machines with Office 2007 on them, mine included. I can create an additional Contacts folder, but this doesn't seem to be helping at all. When I 'add to contacts', it adds them to the original contacts folder, not the new one, even if I move it up in the list. I can't find where to remove the original one, either, to force it to add them to the new one. Any ideas? This has started happing on multiple machines, just over the last few weeks.