On Sun, 16 Mar 2014, Re@lබණ්ඩා™ wrote:
Hi All,
Is there a way to disable spam results from been published to the mail header?
Usually, depending upon how spamassassin is hooked into your mail system.
Looking at your example message I don't see any "Checker-Version" header which
normally SA systems add. This tends to indicate that your system is doing some
kind of custom header/results processing. Normal SA systems use configuration
options (see BASIC MESSAGE TAGGING OPTIONS section of SA documentation) to
control this however it appears that you're using SA-Exim, you'll need to check
its documentation for how to configure that.
And I could see two sections of spam results in the mail header as follows.
What could be the reason for that?
At a guess, it appears that this message has gone through some kind of list
processing system, so maybe SA processed twice. Usual SA practice is to remove
(or overwrite) previously existing SA headers when processing a message.
However this, again, is dependent upon how SA is hooked into your mail system.
Bottom line, you've got an unusual SA kit there, time to do some code diving.
From: xxx
To: xxx
Thread-Topic: xxxx
Thread-Index: Ac8/0magIx/1eKsLQWmx3TflU2Na0Q==
Date: Fri, 14 Mar 2014 22:25:53 +0000
Message-ID: <xxxx>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [x.x.x.x]
MIME-Version: 1.0
X-Spam_score: -1.9
X-Spam_score_int: -18
X-Spam_bar: -
X-Spam_report: Spam detection software,
running on the system "xxxxxx.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or
label similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview: xxxxxxxxxx [...]
Content analysis details: (-1.9 points, 4.8 required)
pts rule name description
---- ----------------------
--------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE BODY: HTML included in message
Subject: xxxxx
X-BeenThere: xxxx
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xxxx>
List-Unsubscribe: <xxxxxxx>
List-Archive: <xxxxxxx>
List-Post: <mailto:xxxxx>
List-Help: <mailto:xxxxxxxxxx>,
<mailto:xxxxx>
Content-Type: multipart/mixed; boundary="===============1539826444465457238=="
Sender: xxxxxxxx
Errors-To: xxxxxxxx
X-Spam_score: 1.6
X-Spam_score_int: 16
X-Spam_bar: +
X-Spam_report: Spam detection software, running on the system "xxxxxx.com", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content preview: xxxxxxxx [...]
Content analysis details: (1.6 points, 4.8 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 HTML_MESSAGE BODY: HTML included in message
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4901]
0.8 RDNS_NONE Delivered to internal network by a host with no
rDNS
X-SA-Exim-Connect-IP: x.x.x.x
X-SA-Exim-Mail-From: xxxxxxx
X-SA-Exim-Scanned: No (on xxxxxxxx); SAEximRunCond expanded to false
--
Re@lBanda
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
