Hi,
I'm using SpamAssassin v3.3.1-3 on ClearOS 6.7 (a CentOS derivative)
and I believe it is invoked by amavis-new. I have a whitelist line
in local.cf:
whitelist_from *@avivaemail.co.uk @m.avivaemail.co.uk
*@tomtom.com *@dpd.co.uk *@clearos.com *@peacocks-mail.com
In e-mail headers from clearos.com I get the following:
Return-Path: <nore...@clearos.com>
Received: from localhost (localhost [127.0.0.1])
by server.mydomain.com (Cyrus
v2.3.16-Fedora-RPM-2.3.16-13.v6) with LMTPA;
Mon, 23 May 2016 16:54:24 +0100
X-Sieve: CMU Sieve 2.3
Received: from localhost (localhost [127.0.0.1])
by mailserver.mydomain.com (Postfix) with ESMTP id 15527E506F
for <n...@mydomain.com>; Mon, 23 May 2016 16:54:24 +0100
(BST)
X-Virus-Scanned: amavisd-new at mydomain.com
X-Spam-Flag: NO
X-Spam-Score: -98.893
X-Spam-Level:
X-Spam-Status: No, score=-98.893 tagged_above=-99 required=5
tests=[HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.105,
URIBL_BLOCKED=0.001,
USER_IN_WHITELIST=-100] autolearn=no
Received: from mailserver.mydomain.com ([127.0.0.1])
by localhost (server.mydomain.com [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id M8OSxEPPbP86 for <n...@mydomain.com>;
Mon, 23 May 2016 16:54:23 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
by mailserver.mydomain.com (Postfix) with ESMTP id 10D2AE529A
for <n...@mydomain.com>; Mon, 23 May 2016 16:54:23 +0100
(BST)
Received: from app2-houston.clearsdn.com (antispam3.pointclark.com
[75.125.207.195])
by mailserver.mydomain.com (Postfix) with ESMTP id 919C8DF544
for <n...@mydomain.com>; Mon, 23 May 2016 16:54:22 +0100
(BST)
This looks OK with the X-Spam entries.
From peacocks-mail.com I get:
Return-Path:
<g-22286502917-22331-2200271903-1464103669...@bounce.peacocks-mail.com>
Received: from localhost (localhost [127.0.0.1])
by server.mydomain.com (Cyrus
v2.3.16-Fedora-RPM-2.3.16-13.v6) with LMTPA;
Tue, 24 May 2016 16:27:53 +0100
X-Sieve: CMU Sieve 2.3
Received: from localhost (localhost [127.0.0.1])
by mailserver.mydomain.com (Postfix) with ESMTP id 9228DE8B16
for <ourfam...@mydomain.com>; Tue, 24 May 2016 16:27:53
+0100 (BST)
X-Virus-Scanned: amavisd-new at mydomain.com
Received: from mailserver.mydomain.com ([127.0.0.1])
by localhost (server.mydomain.com [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id 73FALjivwnS1 for <ourfam...@mydomain.com>;
Tue, 24 May 2016 16:27:52 +0100 (BST)
Received: from localhost (localhost [127.0.0.1])
by mailserver.mydomain.com (Postfix) with ESMTP id BCD76E8CB3
for <ourfam...@mydomain.com>; Tue, 24 May 2016 16:27:52
+0100 (BST)
Received: from unusquattuorsx.theta.eccluster.com
(unusquattuorsx.theta.eccluster.com [91.192.41.146])
by mailserver.mydomain.com (Postfix) with ESMTP id 6E6BEE0462
for <ourfam...@mydomain.com>; Tue, 24 May 2016 16:27:52
+0100 (BST)
In this case there are no X-Spam entries, as if whitelisting
completely bypasses spamassassin but both go through amavisd-new.
Can you help me understand what is happening?
Thanks,
Nick
|
- Odd results when using whitelisting Nick Howitt
-
