IronPort - Configuration Guide - AsyncOS 7.6.1

Chapter 9 Anti-Spam
Determining Which Headers are Used
OL-25136-01
Table 9-3 A Series of Received: Headers (Path A Example 2) (Continued)
2 Received: from mx.customerdomain.org (mx.customerdomain.org) [10.2.3.4]) by
mta.customerdomain.org (8.12.11/8.12.11) with ESMTP id j8LKkWu1008155 for
;
3 Received: from sending-machine.spamham.com (sending-machine.spamham.com [7.8.9.1])
by mx.customerdomain.org (Postfix) with ESMTP id 4F3DA15AC22 for
;
Figure 9-15 shows the incoming relay for path A (above) as configured in the Add Relay page in the
GUI:
Figure 9-15 A Configured Incoming Relay
Your Cisco IronPort appliance will only examine the headers that were present when the message was
received. So, additional headers added locally (such as Microsoft Exchange headers, etc.) or when the
message is received by the Cisco IronPort appliance are not processed. One way to help determine which
headers are used is to configure AsyncOS logging to include received headers via the logheaders
subcommand of the logconfig CLI command:
mail3.example.com> logconfig
Currently configured logs:
[ ... list of configured logs ... ]
Choose the operation you want to perform:
- NEW - Create a new log.
- EDIT - Modify a log subscription.
- DELETE - Remove a log subscription.
- SETUP - General settings.
Cisco IronPort AsyncOS 7.6 for Email Configuration Guide
9-25