>Current versions of SpamAssassin won't fire ALL_TRUSTED if it can't
>parse all of the received headers.
>
> Since you provided no current debug info, or even said what version you
> are using, I can only guess at what you're problem might be. Are you
> sure it's not parsing the header and isn't instead a trust path issue?
> Or maybe did you not upgrade (you haven't said that you did) or maybe
> you upgraded to a version that hadn't yet modified the ALL_TRUSTED
> behavior, or maybe...
Hi Daryl,
Here is an email just come in which has been flagged as ALL_TRUSTED.
As you can see from the headers, i have just upgraded to SpamAssassin 3.1.2,
however it still doesn't process the received header.
==========================================
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.1.2 (2006-05-25) on server
X-Spam-Level: ****************
X-Spam-Hammy: 0.088-2526--13131h-2842s--0d--H*M:localhost,
0.109-1441--10639h-2908s--0d--H*MI:localhost
X-Spam-Status: Yes, score=16.9 required=2.4 bayes=1.0000
tests=ALL_TRUSTED,BAYES_99,HTML_MESSAGE,SARE_OEM_A_1,SARE_OEM_A_2,
SARE_OEM_PRODS_1,SARE_OEM_PRODS_FEW,SARE_OEM_S_DOL,
SARE_OEM_S_PRICE,SARE_PRODUCTS_02,URIBL_BLACK,
URIBL_JP_SURBL,URIBL_SC_SURBL autolearn=disabled
version=3.1.2
X-Spam-Spammy: 1.000-190--0h-2333s--0d--6995,
1.000-187--0h-2296s--0d--$49.95
X-Spam-Report:
* -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
* [score: 1.0000]
* 1.2 SARE_OEM_S_DOL RAW: One strike, you're out
* 1.0 SARE_OEM_S_PRICE RAW: CSS style that ends with price
* 1.0 URIBL_JP_SURBL Has URI in JP at
http://www.surbl.org/lists.html
* [URIs: vgaffno.com]
* 2.0 URIBL_BLACK Contains an URL listed in the URIBL blacklist
* [URIs: vgaffno.com]
* 4.5 URIBL_SC_SURBL Contains an URL listed in the SC SURBL
blocklist
* [URIs: vgaffno.com]
* 1.5 SARE_OEM_A_2 More common OEM spam phrases
* 2.0 SARE_OEM_A_1 Common OEM spam phrases
* 0.8 SARE_OEM_PRODS_1 SARE_OEM_PRODS_1
* 0.9 SARE_OEM_PRODS_FEW SARE_OEM_PRODS_FEW
* 0.4 SARE_PRODUCTS_02 SARE_PRODUCTS_02
Received: from [127.0.0.1] by arkbb.co.uk with SMTP (HELO server.)
(ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.8.2)); Mon,
5 Jun 2006 03:48:52 +0100
Received: (from localhost [24.180.47.240])
by server. (NAVGW 2.5.2.12) with SMTP id M2006060503484615455
for <[EMAIL PROTECTED]>; Mon, 05 Jun 2006 03:48:47 +0100
Etc.
==========================================
Here is the relevant part of the SpamAssassin debug log:
==========================================
[4060] dbg: dns: dns_available set to yes in config file, skipping test
[4060] dbg: dns: IP is private, not looking up PTR: 127.0.0.1
[4060] dbg: received-header: parsed as [ ip=127.0.0.1 rdns= helo=
by=arkbb.co.uk ident= envfrom= intl=0 id= auth= ]
[4060] dbg: received-header: relay 127.0.0.1 trusted? yes internal? yes
[4060] dbg: metadata: X-Spam-Relays-Trusted: [ ip=127.0.0.1 rdns= helo=
by=arkbb.co.uk ident= envfrom= intl=1 id= auth= ]
[4060] dbg: metadata: X-Spam-Relays-Untrusted:
[4060] dbg: metadata: X-Spam-Relays-Internal: [ ip=127.0.0.1 rdns= helo=
by=arkbb.co.uk ident= envfrom= intl=1 id= auth= ]
[4060] dbg: metadata: X-Spam-Relays-External:
==========================================
Here you can see that it has only recognised and parsed the one received
header, even though you can clearly see two, albeit one is not correctly
formed.
So from these it seems to me that it can't be a problem with the trusted
path and i believe i am using the latest version.
Thanks for your help,
Ben
