Cisco Cisco Email Security Appliance C170 사용자 가이드
8-37
Cisco IronPort AsyncOS 7.5 for Email Configuration Guide
OL-25136-01
Chapter 8 Anti-Spam
shows the incoming relay for path A (above) as configured in the Add
Relay page in the GUI:
Figure 8-15
A Configured Incoming Relay
Determining Which Headers are Used
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
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:
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 <joefoo@customerdomain.org>;
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
<joefoo@customerdomain.org>;
Table 8-3
A Series of Received: Headers (Path A Example 2) (Continued)
mail3.example.com> logconfig
Currently configured logs: