Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Página de 1211
 
13-15
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
 
Chapter 13      Anti-Spam
  Reporting Incorrectly Classified Messages to Cisco Systems
Reporting Incorrectly Classified Messages to Cisco Systems
Messages that appear to be incorrectly classified may be reported to Cisco for analysis. Each message is 
reviewed by a team of human analysts and used to enhance the accuracy and effectiveness of the product. 
Each message should be forwarded as an RFC 822 attachment to the following addresses:
spam@access.ironport.com - for reporting missed spam 
ham@access.ironport.com - for reporting false-positives 
Due to the volume of submissions, Cisco IronPort cannot provide individual feedback or results to 
customers.
For more information about reporting incorrectly classified messages, please see the Cisco Knowledge 
base or contact your Cisco Support provider. 
Determining Sender IP Address In Deployments with Incoming 
Relays 
If one or more mail exchange/transfer agents (MX or MTA), filtering servers, etc. stand at the edge of 
your network, between your Cisco appliance and the external machines that are sending incoming mail, 
then your appliance cannot determine the IP addresses of the sending machines. Instead, mail appears to 
originate from the local MX/MTA. However, IronPort Anti-Spam and Cisco Intelligent Multi-Scan 
(using the SenderBase Reputation Service) depend on accurate IP addresses for external senders. 
The solution is to configure your appliance to work with incoming relays. You specify the names and IP 
addresses of all of the internal MX/MTAs connecting to the Cisco appliance, as well as the header used 
to store the originating IP address. 
Related Topics
 
 
Example Environments with Incoming Relays 
 shows a very basic example of an incoming relay. Mail from IP address 7.8.9.1 appears to 
come from IP address 10.2.3.4 because the local MX/MTA is relaying mail to the Cisco appliance.