Interesting, but, the domain I'm asking about isn't sinister.net :-)
My current guess is that when the mail processes into amavis, when send from local <> local (all on the same server) the email comes from localhost, triggers SA, localhost isn't in the SPF record, and thus triggers the SPF_NEUTRAL rule.
I"ll probably just fix this by adding localhost to the local domain list (once I figure out how) so SA doesn't check. Would adding ip4:127.0.0.1 ato the SPF record also work?
rick At 07:20 PM 3/11/2009, Martin Gregorie wrote:
On Wed, 2009-03-11 at 15:16 -0400, spamassas...@corwyn.net wrote: > v=spf1 a mx ptr Interesting: I just pointed thre SPF testing tools at http://www.kitterman.com/spf/validate.html at sinister.net. That retrieved: spf1 ip4:75.180.132.0/24 mx include:aspmx.googlemail.com include:mail.zoneedit.com include mail7.zoneedit.com ~all and says its invalid because it doesn't start "v=spf1". I found the SPF record construction difficult, mainly because I didn't think the specification was clear, so I ended up building it using the wizard at http://www.openspf.org/ and then used the Kitterman test tools to check the result. HTH Martin
