Well, that one failed and it wasn't the list-posted copy. That was my direct email.
And the HELO *should* pass due to the inclusion of IP address. It looks like you've got a broken trust path and SA is checking the wrong Received: header. Is your mailserver NATed? Do you have trusted_networks declared? Steve Martin wrote: > Well, it doesn't ;-) > > On Aug 15, 2005, at 6:02 PM, Matt Kettler wrote: > >> Return-Path: <[EMAIL PROTECTED]> >> X-Original-To: [EMAIL PROTECTED] >> Delivered-To: [EMAIL PROTECTED] >> Received: by cheezmo.com (Postfix, from userid 88) >> id 30552EBDC5; Mon, 15 Aug 2005 18:03:32 -0500 (CDT) >> X-Spam-Flag: NO >> X-Spam-Checker-Version: SpamAssassin 3.1.0-rc1 (2005-08-11) on >> closet.local >> X-Spam-Level: >> X-Spam-Hammy: Tokens not available. >> X-Spam-Status: No, score=-5.2 required=5.0 tests=AWL,FORGED_RCVD_HELO, >> SPF_HELO_SOFTFAIL,USER_IN_WHITELIST_TO autolearn=no >> version=3.1.0-rc1 >> X-Spam-Spammy: Tokens not available. >> X-Spam-Tokens: Bayes not run. >> X-Spam-Report: >> * 0.1 FORGED_RCVD_HELO Received: contains a forged HELO >> * -6.0 USER_IN_WHITELIST_TO User is listed in 'whitelist_to' >> * 2.4 SPF_HELO_SOFTFAIL SPF: HELO does not match SPF record >> (softfail) >> * [SPF failed: ] >> * -1.8 AWL AWL: From: address is in the auto white-list >> Received: from xanadu.evi-inc.com (xan.evitechnology.com >> [208.39.141.86]) >> by cheezmo.com (Postfix) with ESMTP id 816AAEBDBA >> for <[EMAIL PROTECTED]>; Mon, 15 Aug 2005 18:02:57 -0500 (CDT) >> Received: from [10.0.6.1] (EVI802-275.evitechnology.com [10.0.6.1]) >> (authenticated bits=0) >> by xanadu.evi-inc.com (8.12.8/8.12.8) with ESMTP id j7FN27bt005517; >> Mon, 15 Aug 2005 19:02:07 -0400
