You Cannot Send Encrypted E-Mail Messages to a Contact While You Are Working Offline (326311)



The information in this article applies to:

  • Microsoft Outlook 2002 Service Pack 1 (SP-1)
  • Microsoft Outlook 2002 Service Pack 2 (SP-2)

This article was previously published under Q326311

SYMPTOMS

If you are using certificates to digitally encrypt your e-mail messages in Outlook 2002, and if all the following conditions are true
  • You are working in offline mode.

    -and-
  • You are sending the e-mail message to another Microsoft Exchange security-enabled recipient.
Outlook 2002 sends the e-mail message unencrypted, and you receive the following message:

Microsoft Outlook had problems encrypting this message because the following recipients had missing or invalid certificates, or conflicting or unsupported encryption capabilities:
[recipient email address]>
Continue will encrypt and send the message but the listed recipients may not be able to read it.

If you try to send the same encrypted e-mail message to the same recipient while you are working online, Outlook 2002 successfully encrypts and sends the e-mail message.

CAUSE

This problem occurs if all the following conditions are true:
  • You have a contact in your Microsoft Outlook mailbox for the recipient.

    -and-
  • Outlook 2002 uses the contact information for the recipient in the Outlook mailbox instead of using the information for the recipient that is in the offline Address Book to find the recipient's certificate.

    -and-
  • The contact information in the Outlook mailbox does not have updated certificate information for the recipient.

RESOLUTION

Service Pack Information

This problem is corrected in Office XP Service Pack 3.

To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307841 How to obtain the latest Office XP Service Pack

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.



The global version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version         Size       File name
   ------------------------------------------------------------
   16-Aug-2002  21:05  10.0.4413.0       346,696  Exsec32.dll      
   09-Aug-2002  03:22  10.0.4406.0       137,800  Impmail.dll      
   13-Sep-2002  03:52  10.0.4510.0       539,208  Outlcm.dll       
   13-Sep-2002  03:52  10.0.4510.0     6,310,472  Outllib.dll      
   13-Sep-2002  03:52  10.0.4510.0        92,744  Outlmime.dll     
   13-Sep-2002  03:52  10.0.4510.0        47,688  Outlook.exe      
   09-Aug-2002  03:22  10.0.4406.0       121,416  Outlph.dll   
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

This problem was first corrected in Office XP Service Pack 3.

Modification Type:MinorLast Reviewed:7/28/2006
Keywords:kbHotfixServer kbQFE kbofficexppresp3fix kbQFE kbbug kbfix KB326311