"Brian Tillman" wrote:
> rev michael <revmichael@discussions.microsoft.com> wrote:
>
> > I don't know what to think. As another course of action, I subscribed
> > to a didgital id from another source, other than VeriSign, and
> > received the exact same results, when installing/associating.
> >
> > Maybe it is some setting in my IE7, that does not allow in import of
> > the private key with the cert.
>
> We get certs from VeriSign and all allow the exportation of the private key,
> except for those who decided not to back up their certs as I told them to
> when they requested one, and then changed their PC or user account and
> wonder why they can't read encrupted mail any more. I use IE7 and don't
> have the problem you describe.
>
> While I don't understand the underlying data structures of the crytpo store
> IE uses, may things can go wrong. With about 150 people here having
> certificates, I've run into a lot of them. Unless you have your own PKI
> infrastructure with private key recovery, certs tend to be fragile, at least
> in my opinion. Your symptoms sound to me like a damaged WIndows user
> profile. Is there any way you could try this with a new Windows user? You
> might have to get a new cert to test or, perhaps, try to download it again
> from VeriSign. Thawte provides free mail certs for personal use, I believe,
> and you could test with one of those.
> --
> Brian Tillman
>
>
I think MichaelR and "rev michael" are the same person Brian. But that is
niether hear nore there since this thread is over a year old.
Sorry to chime in on this thread at such a late date.
I am having a similar issue s/mime certificates, but we're encountering it
on an inbound encrypted message. The same message is displayed when trying
to open the encrypted email. This seems to suggest that somehow Outlook does
not have access to the IE7 certificate store. Is there a specific setting in
Outlook or IE7 to can be inadvertantly set during an update thay may cause
this.
We have multiple customers running Outlook 2003 on XP w/ IE7 and they all
are issued the same pkcs12 certificate, but a few of them run into this issue
where "Your Digital ID Name cannot be found".