Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1181
 
13-18
User Guide for AsyncOS 9.8 for Cisco Email Security Appliances
 
Chapter 13      Anti-Spam
  Determining Sender IP Address In Deployments with Incoming Relays
Missed phishing message - 
phish@access.ironport.com
You can achieve best results if you use one of the following email programs to forward the message:
Apple Mail
Microsoft Outlook for Mac
Microsoft Outlook Web App
Mozilla Thunderbird
Caution
If you are using Microsoft Outlook 2010, 2013, or 2016 for Microsoft Windows, you must use the Cisco 
Email Security Plug-In or the Microsoft Outlook Web App to report incorrectly classified messages. This 
is because Outlook for Windows may not forward the message with the required headers intact. Also, 
use the mobile platforms only if you can forward the original message as an attachment. 
How to Track Your Submissions
After your receive an email notification with the submission details, you can view and track your 
submission on Cisco Email Submission and Tracking Portal.
Procedure
Step 1
Log in to Cisco SecurityHub (
) using your Cisco credentials. 
Step 2
Click Email Submission and Tracking.
Step 3
Click Submissions.
Step 4
Use the filters (Time Duration, Submission ID, Subject, Submitter, and Status) to find your submission.
For more information, see 
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