Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1181
 
41-20
User Guide for AsyncOS 9.8 for Cisco Email Security Appliances
 
Chapter 41      Testing and Troubleshooting
  Troubleshooting Email Delivery From the Appliance
If you cannot connect from one interface to another, you may have issues with the way in which the 
appliance’s Management and Data1 and Data2 interfaces are connected to your network. See 
 for more information. You can telnet to port 25 of the 
listener and enter SMTP commands manually (if you are familiar with the protocol). 
Examine the IronPort text mail logs and injection debug logs to check for receiving errors. 
Injection debug logs record the SMTP conversation between the appliance and a specified host 
connecting to the system. Injection debug logs are useful for troubleshooting communication 
problems between the appliance and a client initiating a connection from the Internet. The log 
records all bytes transmitted between the two systems and classifies them as “Sent to” the 
connecting host or “Received from” the connecting host.
For more information, see 
Troubleshooting Email Delivery From the Appliance
If you suspect problems with delivering email from the appliance, try the following strategies:
Determine if the problem is domain-specific.
Use the 
tophosts
 command to get immediate information about the email queue and determine if a 
particular recipient domain has delivery problems. 
Are there problem domains returned when you sort by “Active Recipients?” 
2. Management (192.168.42.42/24: mail3.example.com)
3. PrivateNet (192.168.1.1/24: mail3.example.com)
4. PublicNet (192.168.2.1/24: mail3.example.com)
[1]> 3
Enter the remote hostname or IP.
[]> 193.168.1.1
Enter the remote port.
[25]> 25
Trying 193.168.1.1...
Connected to 193.168.1.1.
Escape character is '^]'.