R
raymejr
Hello,
Please be patient with me as I'm not the most computer literate person
in the world... LOL!
My issue is that I recently obtained a 'digital certificate' from a
company called Versign, so I could communicate with a co-worker of mine
who needs to send over REI contracts via encryption. Once the two of us
purchased our digital ids from VerSign and went through the necessary
steps to swap signed emails, now when ever I send my co-worker an email
encrypted, when they open it, the receive some type of warning which
indicates the email has been tampered.
We have attempted to see if maybe VerSign support would be able to
assist us, but they indicated that since they could not reproduce the
issue in their testing facility, and that internally they use OL 2003
as well and have never encountered such an issue, directed me to
contact MS support directly, but seeing as I'm self-emplyeed, I cant'
really afford to come out of pocket the needed dollar amount to talk to
MS Support at the moment, so Im hoping someone here might be able to
tell what might be causing this issue to arise by chance?
If needed, my co-worker and myself are both running OL2003 with all the
latest patches/fixes installed and all email is sent through my Comcast
account.
If anyone could point to a web site, which doesn't have to be MS link,
which outlines why this is occuring, I'd would be GREATLY appreciated.
Thank you,
Raymond M. Estes Jr.
Please be patient with me as I'm not the most computer literate person
in the world... LOL!
My issue is that I recently obtained a 'digital certificate' from a
company called Versign, so I could communicate with a co-worker of mine
who needs to send over REI contracts via encryption. Once the two of us
purchased our digital ids from VerSign and went through the necessary
steps to swap signed emails, now when ever I send my co-worker an email
encrypted, when they open it, the receive some type of warning which
indicates the email has been tampered.
We have attempted to see if maybe VerSign support would be able to
assist us, but they indicated that since they could not reproduce the
issue in their testing facility, and that internally they use OL 2003
as well and have never encountered such an issue, directed me to
contact MS support directly, but seeing as I'm self-emplyeed, I cant'
really afford to come out of pocket the needed dollar amount to talk to
MS Support at the moment, so Im hoping someone here might be able to
tell what might be causing this issue to arise by chance?
If needed, my co-worker and myself are both running OL2003 with all the
latest patches/fixes installed and all email is sent through my Comcast
account.
If anyone could point to a web site, which doesn't have to be MS link,
which outlines why this is occuring, I'd would be GREATLY appreciated.
Thank you,
Raymond M. Estes Jr.