Spam
同一封電子郵件對於一個使用者被評估為垃圾郵件,而對於另一個使用者則被評估為正常郵件
我有郵件伺服器,安裝了 spamassassin 來過濾垃圾郵件。
我面臨的問題是,在 02h 第一個使用者收到的電子郵件被視為垃圾郵件(並且是真正的垃圾郵件,移至垃圾郵件文件夾,沒關係)。
但在 07 時,另一位使用者收到了相同的電子郵件,但並未將其視為垃圾郵件。
你能告訴我為什麼會發生這種情況以及為什麼第二封電子郵件沒有被視為垃圾郵件嗎?
由於您提供的資訊有限,不。
但是您有不同的個人使用者偏好和可能的個人貝氏數據庫?
您確實知道 SpamAssassin 會添加帶有觸發規則的標頭以及生成的垃圾郵件分數,例如比較正常郵件:
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on ... X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,FREEMAIL_FROM, HTML_MESSAGE,RP_MATCHES_RCVD autolearn=ham version=3.3.1
對於垃圾郵件的冗長垃圾郵件報告:
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on X-Spam-Flag: YES X-Spam-Level: ********************** X-Spam-Status: Yes, score=23.0 required=5.0 tests=BAYES_99,FSL_HELO_BARE_IP_2, MSGID_FROM_MTA_HEADER,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_BRBL_LASTEXT, RCVD_IN_PSBL,RCVD_IN_SORBS_WEB,RCVD_NUMERIC_HELO,RDNS_DYNAMIC,TVD_RCVD_IP, TVD_RCVD_IP4,URIBL_AB_SURBL,URIBL_DBL_SPAM,URIBL_JP_SURBL,URIBL_WS_SURBL autolearn=spam version=3.3.1 X-Spam-Report: * 4.5 URIBL_AB_SURBL Contains an URL listed in the AB SURBL blocklist * [URIs: behoop.ru] * 1.6 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist * [URIs: behoop.ru] * 1.2 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist * [URIs: behoop.ru] * 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist * [URIs: behoop.ru] * 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100% * [score: 1.0000] * 0.0 TVD_RCVD_IP4 TVD_RCVD_IP4 * 0.0 TVD_RCVD_IP TVD_RCVD_IP * 1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO * 2.7 RCVD_IN_PSBL RBL: Received via a relay in PSBL * [46.185.20.237 listed in psbl.surriel.com] * 0.8 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server * [46.185.20.237 listed in dnsbl.sorbs.net] * 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net * [Blocked - see <http://www.spamcop.net/bl.shtml?46.185.20.237>] * 1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT * [46.185.20.237 listed in bb.barracudacentral.org] * 1.0 RDNS_DYNAMIC Delivered to internal network by host with * dynamic-looking rDNS * 0.0 MSGID_FROM_MTA_HEADER Message-Id was added by a relay * 2.0 FSL_HELO_BARE_IP_2 FSL_HELO_BARE_IP_2