Cisco Cisco Email Security Appliance C390 Weißbuch

Seite von 11
Successful TLS connection from remote host (Receiving):
Wed Jul 20 19:47:40 2005 Info: New smtp ICID 282204970 interface 
Management
(10.10.10.1) address 192.168.1.1 reverse dns host unknown verified no
Wed Jul 20 19:47:40 2005 Info: ICID 282204970 ACCEPT SG None 
match SBRS None
Wed Jul 20 19:47:40 2005 Info: ICID 282204970 TLS success
Wed Jul 20 19:47:40 2005 Info: Start MID 200257070 ICID 282204970
Failed TLS connection from remote host (Receiving):
Tue Jun 28 19:08:49 2005 Info: New SMTP ICID 282204971 interface 
Management
(10.10.10.1) address 192.168.1.1 reverse dns host unknown verified no
Tue Jun 28 19:08:49 2005 Info: ICID 282204971 ACCEPT SG None 
match SBRS None
Tue Jun 28 19:08:49 2005 Info: ICID 282204971 TLS failed
Tue Jun 28 19:08:49 2005 Info: ICID 282204971 lost
Tue Jun 28 19:08:49 2005 Info: ICID 282204971 TLS was required but 
remote host
did not initiate it
Tue Jun 28 19:08:49 2005 Info: ICID 282204971 close
Successful TLS connection to remote host (Delivery):
Tue Jun 28 19:28:31 2005 Info: DCID 2386069 TLS success CN: 
<common>
Tue Jun 28 19:28:31 2005 Info: New SMTP DCID 2386069 interface 
10.10.10.2 
address 192.168.2.2
Tue Jun 28 19:28:31 2005 Info: Delivery start DCID 2386069 MID 
200257075 to RID [0]
Failed TLS connection to remote host (Delivery):
Fri Jul 22 22:00:05 2005 Info: DCID 2386070 IP 192.168.2.2 TLS 
failed: STARTTLS
unexpected response
The Performance Impact of TLS Encryption
A single TLS connection requires the same amount of server resources 
as approximately ten clear text conversations.
To mitigate the performance impact, there is a limit to the number of 
simultaneous TLS connections.
You can set the limits for inbound and outbound TLS connections per 
your requirements. If the connection limit is reached for outbound 
connections, Cisco Email Security will negotiate a clear text 
conversation with partners whose MTA (message transfer agent) allows 
it. Where the partner has TLS required, Cisco Email Security will simply 
wait and try the connection again later.
© 2016 Cisco and/or its affiliates. All rights reserved. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, 
go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco 
and any other company. (1110R) 
C07-737950-00  11/16
How-To Secure Communications -  
Setting Up Transport Layer Security (TLS)
Cisco Public