You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Carsten <ca...@schiers.de> on 2006/09/14 16:39:36 UTC
Why is ALL_TRUSTED fireing here?
Hi,
I am wondering, why for a certain email, ALL_TRUSTED is still fireing.
Sometimes, it works.
Sometimes not. I use fetchmail by the way to fetch mail from a provider. I
put 127 and my
local net into internal, these plus the provider into trusted.
I put below some headers and a snip from my local.cf and a snip from
spamassassin -t -D.
After recognizing it's fetchmail, it doesn't parse eny more.
Just to proof, I also put headers and debug output of a working case at the
end.
BTW: it's 3.0.3
Thanks for any hint,
Carsten.
Headers:
=====
Return-Path: <el...@meramer.com>
Received: from data.voyager.zz ([unix socket])
by data (Cyrus v2.1.18-IPv6-Debian-2.1.18-1+sarge2) with LMTP; Tue,
25 Jul 2006 14:50:16 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost ([127.0.0.1] helo=localhost.localdomain)
by data.voyager.zz with esmtp (Exim 4.50)
id 1G5MMV-0007PR-VG
for carsten@localhost; Tue, 25 Jul 2006 14:50:15 +0200
Received: from localhost (localhost.localdomain [127.0.0.1])
by localhost.localdomain (AvMailGate-2.0.2-15) id 28480-588B7830;
Tue, 25 Jul 2006 14:50:11 +0200
Received: from pop.1und1.com [212.227.15.177]
by localhost with POP3 (fetchmail-6.2.5)
for carsten@localhost (single-drop); Tue, 25 Jul 2006 14:50:11 +0200
(CEST)
Received: from [200.101.95.54]
(helo=200-101-95-54.bsace702.dsl.brasiltelecom.net.br)
by mx.kundenserver.de (node=mxeu1) with ESMTP (Nemesis),
id 0MKpV6-1G5MML2KRo-0005M4 for carsten@schiers.de; Tue, 25 Jul 2006
14:50:03 +0200
Received: from mail.rockforce.net
by 200-101-95-54.bsace702.dsl.brasiltelecom.net.br (8.9.3/8.9.3)
with ESMTP id wIlQfxGMUX0n
for <ca...@schiers.de>; Tue, 25 Jul 2006 08:45:13 -0400
Received: from 177.220.152.6
by mail.rockforce.net with ESMTP (Exim 4.05) id PzYGG0srVECK
for <ca...@schiers.de>; Tue, 25 Jul 2006 08:45:13 -0400
Received-SPF: none (mxeu1: 200.101.95.54 is neither permitted nor denied by
domain of meramer.com) client-ip=200.101.95.54;
envelope-from=ellynigg@meramer.com;
helo=200-101-95-54.bsace702.dsl.brasiltelecom.net.br;
From: "Kareem Campos" <el...@meramer.com>
Reply-To: "Kareem Campos" <el...@meramer.com>
Message-ID: <96...@meramer.com>
Date: Tue, 25 Jul 2006 08:45:13 -0400
To: <ca...@schiers.de>
snip from local.cf:
===========
clear_internal_networks
internal_networks 127/8
internal_networks 192.168.9/8
clear_trusted_networks
trusted_networks 127/8
trusted_networks 192.168.9/8
trusted_networks 212.227.15/8
snip from debug output:
===============
debug: received-header: unknown format: from data.voyager.zz ([unix socket])
by data (Cyrus v2.1.18-IPv6-Debian-2.1.18-1+sar
ge2) with LMTP; Thu, 20 Jul 2006 21:23:43 +0200
debug: received-header: parsed as [ ip=127.0.0.1 rdns=localhost
helo=localhost.localdomain by=data.voyager.zz ident= envfrom
= intl=0 id=1G3e7T-0005gd-Vb auth= ]
debug: received-header: parsed as [ ip=127.0.0.1 rdns=localhost.localdomain
helo=localhost by=localhost.localdomain ident= e
nvfrom= intl=0 id=21858-2F8A35BE auth= ]
debug: found fetchmail marker, restarting parse
debug: metadata: X-Spam-Relays-Trusted:
debug: metadata: X-Spam-Relays-Untrusted:
headers, when it's working:
=================
Return-Path: <el...@meramer.com>
Received: from data.voyager.zz ([unix socket])
by data (Cyrus v2.1.18-IPv6-Debian-2.1.18-1+sarge2) with LMTP; Tue,
25 Jul 2006 14:50:16 +0200
X-Sieve: CMU Sieve 2.2
Received: from localhost ([127.0.0.1] helo=localhost.localdomain)
by data.voyager.zz with esmtp (Exim 4.50)
id 1G5MMV-0007PR-VG
for carsten@localhost; Tue, 25 Jul 2006 14:50:15 +0200
Received: from localhost (localhost.localdomain [127.0.0.1])
by localhost.localdomain (AvMailGate-2.0.2-15) id 28480-588B7830;
Tue, 25 Jul 2006 14:50:11 +0200
Received: from pop.1und1.com [212.227.15.177]
by localhost with POP3 (fetchmail-6.2.5)
for carsten@localhost (single-drop); Tue, 25 Jul 2006 14:50:11 +0200
(CEST)
Received: from [200.101.95.54]
(helo=200-101-95-54.bsace702.dsl.brasiltelecom.net.br)
by mx.kundenserver.de (node=mxeu1) with ESMTP (Nemesis),
id 0MKpV6-1G5MML2KRo-0005M4 for carsten@schiers.de; Tue, 25 Jul 2006
14:50:03 +0200
Received: from mail.rockforce.net
by 200-101-95-54.bsace702.dsl.brasiltelecom.net.br (8.9.3/8.9.3)
with ESMTP id wIlQfxGMUX0n
for <ca...@schiers.de>; Tue, 25 Jul 2006 08:45:13 -0400
Received: from 177.220.152.6
by mail.rockforce.net with ESMTP (Exim 4.05) id PzYGG0srVECK
for <ca...@schiers.de>; Tue, 25 Jul 2006 08:45:13 -0400
Received-SPF: none (mxeu1: 200.101.95.54 is neither permitted nor denied by
domain of meramer.com) client-ip=200.101.95.54;
envelope-from=ellynigg@meramer.com;
helo=200-101-95-54.bsace702.dsl.brasiltelecom.net.br;
From: "Kareem Campos" <el...@meramer.com>
Reply-To: "Kareem Campos" <el...@meramer.com>
Message-ID: <96...@meramer.com>
Date: Tue, 25 Jul 2006 08:45:13 -0400
To: <ca...@schiers.de>
debug log, if it's working:
================
debug: received-header: unknown format: from data.voyager.zz ([unix socket])
by data (Cyrus v2.1.18-IPv6-Debian-2.1.18-1+sar
ge2) with LMTP; Tue, 25 Jul 2006 14:50:16 +0200
debug: received-header: parsed as [ ip=127.0.0.1 rdns=localhost
helo=localhost.localdomain by=data.voyager.zz ident= envfrom
= intl=0 id=1G5MMV-0007PR-VG auth= ]
debug: received-header: parsed as [ ip=127.0.0.1 rdns=localhost.localdomain
helo=localhost by=localhost.localdomain ident= e
nvfrom= intl=0 id=28480-588B7830 auth= ]
debug: found fetchmail marker, restarting parse
debug: received-header: parsed as [ ip=177.220.152.6 rdns=177.220.152.6
helo= by=mail.rockforce.net ident= envfrom= intl=0 i
d=PzYGG0srVECK auth= ]
debug: received-header: relay 177.220.152.6 trusted? no internal? no
debug: metadata: X-Spam-Relays-Trusted:
debug: metadata: X-Spam-Relays-Untrusted: [ ip=177.220.152.6
rdns=177.220.152.6 helo= by=mail.rockforce.net ident= envfrom=
intl=0 id=PzYGG0srVECK auth= ]
--
View this message in context: http://www.nabble.com/Why-is-ALL_TRUSTED-fireing-here--tf2272019.html#a6307296
Sent from the SpamAssassin - Users forum at Nabble.com.
Re: Why is ALL_TRUSTED fireing here?
Posted by Carsten <ca...@schiers.de>.
OK, solved by an upgrade to 3.1.4
--
View this message in context: http://www.nabble.com/Why-is-ALL_TRUSTED-fireing-here--tf2272019.html#a6313754
Sent from the SpamAssassin - Users forum at Nabble.com.