The information in this article applies to:
SYMPTOMSWhen you send SMTP messages from an Internet Mail Service-enabled client to an Exchange Server computer, you may want these documents sent in a secure fashion. When you configure an e-mail client, for example Outlook Express, to communicate by means of Secure Socket Layer (SSL) for this reason, you may receive the following error message: This indicates that the client was unable to connect to the server. There will not be any event logged on the Exchange Server computer. CAUSE
Microsoft clients configured to send SMTP message by means of SSL are not able to communicate correctly with the Exchange Server computer. When SSL is enabled on an e-mail client, the communication port defaults to port 465, defined by Netscape. When the client issues an SMTP command to send a message, the Internet Mail Service does not receive the communication because it is monitoring port 25. RESOLUTIONAt this time, SSL-enabled Microsoft Internet mail clients send security command requests (SSL) that are incompatible with the Exchange Server Internet Mail Service security command set (TLS). Consequently, there is no way of using this configuration for sending SMTP secure mail. Outlook Express 5, as well as Outlook 2000, will include support for TLS over port 25. Both of these products will support the TLS command set. WORKAROUNDThere are a two workarounds that will work until the Outlook Express 5 and Outlook 2000 products are released.
For additional information, please see the following article in the Microsoft Knowledge Base: Q180979 OL97: Using Outlook with a PPTP Connection-or- MORE INFORMATIONAdditional information on the following subjects can be found at the following locations: TLSftp://ftp.isi.edu/in-notes/rfc2246.txt Communication using PPTPhttp://support.microsoft.com/support/ntserver/serviceware/nts40/e9msg5uxd.asp Message EncryptionQ197974 XCLN: How to Send Encrypted Mail to a User in Another Org Additional query words:
Keywords : |
Last Reviewed: November 5, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |