Outlook security matching certificates with email addresses

P

pjeevan

Hello,

I'm using Win2K SP4, Outlook 2002 with SP2.

I have my own Windows Certificate services with CA and issued a user
certificate (with email encryption...) to say a user [email protected]. I
installed that certificate in my Outlook 2002 using standard procedures,
it installed fine. Now, the user e-mail/reply address in the e-mail
account profile has a different e-mail address, say
[email protected].

Now, anytime I try to send a e-mail with digital signature/encryption, I
get an error message saying

Microsoft Outlook could not sign or encrypt this message because you
have no certificates which can be used to send from the e-mail address
"[email protected]

Searching newsgroups and MS KB found this article which seems to provide
a fix for the problem,
http://support.microsoft.com/default.aspx?scid=kb;en-us;276597 but it
does not work for me. I have used the RegMon tool to monitor the
registry activity and see that the Outlook is not even looking for
SupressNameChecks value.

Does anybody have a suggestion as to how I can get around this problem
and use the certificate that was issued with a different e-mail address
than the e-mail address provided in the account profile?

Thanks in advance.
P
 
P

pjeevan

Hello,

I guess, I answered this issue myself. Basically, I had to add the
keys/values mentioned in the MS KB
http://support.microsoft.com/default.aspx?scid=kb;en-us;276597 in the
HKCU and not in the HKLM as mentioned in that article.

In addition, in the same path in the registry, I had to add another
value 'EnableSRFeatures' and set it 1 (one) as well.

Once I did this, it is working fine.

Hope this helps somebody else as well.

P
 
P

pjeevan

Hello,

For the benefit of other users....

I guess, I found the solution for this myself. I had to add 2 registry
values (SupressNameChecks and EnableSRFeatures), one of which is
mentioned in the MS KB http://support.microsoft.com/default.aspx?
scid=kb;en-us;276597. However, in contrast to what is described in the
MS KB, I had to add those values in the registry in HKCU and not in
HKLM. Having it in HKLM did not work.

Once added those values in the HKCU, it started to work fine.

P
 
Top