Wil Decius wrote:
I'm trying to get Spamassassin local configuration setup to whitleist-by-SPF. The box, as delivered to me, runs Debian withspamassassin -V SpamAssassin version 3.2.5-r609689 running on Perl version 5.8.8 In local.cf I've added whitelist_from_spf [EMAIL PROTECTED] Checking the "target" SPF record it looks OK. dig TXT technologyladder.com +short "v=spf1 mx ip4:64.14.60.0/27 ip4:64.14.53.64/26 ip4:67.151.144.115/32 ip4:64.20.188.0/24 ip4:64.210.209.0/24 ip4:165.193.208.0/24 ip4:165.193.209.0/24 ip4:165.193.210.0/24 ip4:165.193.211.0/24 -all" But email received FROM the "target" does NOT get whitelisted. The message headers contain From: [EMAIL PROTECTED] Return-Path: <[EMAIL PROTECTED]> X-Spam-Report: * 1.5 FH_RELAY_NODNS We could not determine your Reverse DNS * -0.0 SPF_PASS SPF: sender matches SPF record * 5.0 BOTNET Relay might be a spambot or virusbot * [botnet0.8,ip=165.193.208.162,rdns=r14nj3ip1.idc.technologyladder.com,maildomain=technologyladder.com,client,clientwords] * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.5 BAYES_50 BODY: Bayesian spam probability is 40 to 60% * [score: 0.4966] * 1.5 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 0.3 AWL AWL: From: address is in the auto white-list Received: from r14nj3ip1.idc.technologyladder.com ([165.193.208.162] verified) by mail.mydomain.com (SMTP) with ESMTP id 6850528 for [EMAIL PROTECTED]; Fri, 11 Jul 2008 02:28:10 -0700 Received: from unknown (HELO script1.idc.theladders.com) ([10.0.1.221]) by r14nj3ip1.idc.technologyladder.com with ESMTP; 11 Jul 2008 05:28:08 -0400 What do I need to add/change so SPF Whitelisting works? Wil
If mail is forwarded by a trusted hop before SA, you need always_trust_envelope_sender=1
