OL98: Error Replying to an Encrypted Message

ID: Q216075

The information in this article applies to:

Microsoft Outlook 98

NOTE: These procedures only apply if you have installed Outlook with the Corporate or Workgroup option. This option allows you to use Messaging Application Programming Interface (MAPI) services. To determine your installation type, on the Help Menu click About Microsoft Outlook. In About Microsoft Outlook you should see "Corporate or Workgroup" if you have the Corporate or Workgroup installation.

SYMPTOMS

When you reply to an encrypted message received from a non-Microsoft Exchange user, the following error message may appear:

None of the recipients can process an encrypted message. You can either proceed with an unencrypted message or cancel the operation.

CAUSE

Microsoft Outlook is not using the Contact record containing the addressee's security certificate (digital ID) to address the message. Therefore, it assumes the addressee cannot read an encrypted message.

RESOLUTION

Clear the pre-populated e-mail address from the message's To line, and re-address it using the Contact record that contains the addressee's digital ID.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

When replying to a message, Outlook populates the To line of the reply with the address in the From line of the original message. In doing so, it does not resolve the addresses to the local Contact Address Book, which contains the certificates. Without a valid certificate for each recipient, encrypted messages cannot be sent. Because Outlook does not send an unencrypted response to an encrypted message without explicit approval of the user, the error message appears.

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

Q182730 OL98: ErrMsg "Non-Secure Recipients ..."

Additional query words: 98


Keywords          : kbdta Gnlsec MsgRply 
Version           : WINDOWS:
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: April 16, 1999