Return-Path: X-Original-To: apmail-spamassassin-users-archive@www.apache.org Delivered-To: apmail-spamassassin-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B246C6F21 for ; Wed, 13 Jul 2011 16:32:14 +0000 (UTC) Received: (qmail 83182 invoked by uid 500); 13 Jul 2011 16:32:11 -0000 Delivered-To: apmail-spamassassin-users-archive@spamassassin.apache.org Received: (qmail 83142 invoked by uid 500); 13 Jul 2011 16:32:11 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 83135 invoked by uid 99); 13 Jul 2011 16:32:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 16:32:10 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=10.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of darxus@chaosreigns.com designates 64.71.152.40 as permitted sender) Received: from [64.71.152.40] (HELO panic.chaosreigns.com) (64.71.152.40) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 16:32:05 +0000 Received: by panic.chaosreigns.com (Postfix, from userid 1000) id 35DD3325995; Wed, 13 Jul 2011 12:31:43 -0400 (EDT) Date: Wed, 13 Jul 2011 12:31:43 -0400 From: darxus@chaosreigns.com To: users@spamassassin.apache.org Subject: Re: Skipping header lines Message-ID: <20110713163142.GE20505@chaosreigns.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Checked: Checked by ClamAV on apache.org On 07/13, Jason Ede wrote: > I’m running 3.3.2 and I’d like to ignore the first received header as I > receive the email on one postfix instance and then pass it along to > another to do the scanning. So far all the emails are showing up as > trusted as it sees the email as coming from 127.0.0.1 Really? SA should already be skipping any 127.0.0.1 lines. Best to provide a couple examples via something like pastebin.com. Generally you would skip Received headers via the internal_networks configuration setting. But I believe the default is to consider 127.0.0.1 included. -- "It is better to die on your feet than to live on your knees." - Emiliano Zapata, Mexican Revolution Leader http://www.ChaosReigns.com