大家好

環境是 Exchange 2010，前端有一個Cisco的email gateway，名字叫Ironport，用來防毒跟防垃圾郵件。

Exchange 沒有開啟anti-spam這個功能。

老闆反應有一封很重要的信件被丟到outlook的垃圾郵件裡面，他希望下次不要再發生。

我看了一下Header，發現裡面就是沒有 X-MS-Exchange-Organization-SCL 這個資訊，

讓我無從判斷為什麼這封信被丟到垃圾郵件。

請問是因為前面有一台email gateway的關係，所以outlook才看不到SCL的資訊嗎?

還是因為Exchange沒有開啟anti-spam這個功能?

這封信的來源IP很早就在email gateway的白名單裡面，也就是不會過濾spam，直接往後丟給Exchange，

照理說Ironport應該會跟Exchange講這封信的IP在我的白名單裡面，不用過濾spam，

那為什麼Exchange 還會認為這封信是Spam呢?

以下是這封信的Header:

Received: from ironport.xxx.com (192.168.x.x) by aaa.com
(192.168.x.x) with Microsoft SMTP Server id 14.3.235.1; Tue, 9 Apr 2019
20:35:59 +0800
X-IronPort-AV: E=Sophos;i="5.60,329,1549900800";
d="scan'208,217";a="24934021"
Received: from bbb.com ([52.x.x.x]) by
xxx.com with ESMTP/TLS/ADH-AES256-GCM-SHA384; 09 Apr 2019
20:35:59 +0800
Received: from xxx
(xxx.com [52.x.x.x]) by
mail.xxx.com (Postfix) with ESMTP id A1BD8814D5;
Tue, 9 Apr
2019 12:35:58 +0000 (UTC)
From: Maxx xxx@xxx.com
Reply-To: xxx@xxx.com
To: ixxx@xxx.com
Message-ID: 743142920.01554813358479.JavaMail.tomcat7@mail.xxx.com
Subject: Contacting xxx :
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-Path: ankxxx@xxx.com
Date: Tue, 9 Apr 2019 20:35:59 +0800
X-MS-Exchange-Organization-OriginalArrivalTime: 09 Apr 2019 12:35:59.7744
(UTC)
X-MS-Exchange-Forest-ArrivalHubServer: xxxcom
X-MS-Exchange-Organization-OriginalClientIPAddress: 52.x.x.x
X-MS-Exchange-Organization-OriginalServerIPAddress: 192.168.x.x
X-MS-Exchange-Organization-AuthSource: xxx.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-MessageDirectionality: Incoming
X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: xxx.com
X-MS-Exchange-Organization-OriginalSize: 1553
X-MS-Exchange-Forest-MessageScope: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Organization-MessageScope: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Organization-HygienePolicy: Standard
X-MS-Exchange-Organization-MessageLatency: SRV=ironport.xxx.com:TOTAL=0
X-MS-Exchange-Organization-Recipient-Limit-Verified: True
X-MS-Exchange-Forest-RulesExecuted: xxx
MIME-Version: 1.0