All of my emails pass through an antivirus gateway which is the same
server as the mailserver and appears like this in the headers:
Received: from [127.0.0.1] by arkbb.co.uk with SMTP (HELO server.)
(ArGoSoft Mail Server Pro for WinNT/2000/XP, Version 1.8 (1.8.8.9));
Mon, 26 Feb 2007 15:41:04 +0000
Received: from d8-138.rb.vp.centurytel.net ([66.112.83.179])
by server. (NAVGW 2.5.2.12) with SMTP id M2007022615343332143
So all emails come via this trusted relay (127.0.0.1) which is also
internal.
SPF in SpamAssassin is happy to check the HELO:
[2408] dbg: spf: checking HELO (helo=d8-138.rb.vp.centurytel.net,
ip=66.112.83.179)
[2408] dbg: spf: query for /66.112.83.179/d8-138.rb.vp.centurytel.net:
result: none, comment: SPF: domain of sender d8-138.rb.vp.centurytel.net
does not designate mailers
but then refuses to do any more, as it claims not to be able to trust
the X-Envelope-From header because it has been through my AV gateway:
[2408] dbg: spf: relayed through one or more trusted relays, cannot use
header-based Envelope-From, skipping
Similarly:
[2408] dbg: spf: def_spf_whitelist_from: could not find useable envelope
sender
[2408] dbg: spf: spf_whitelist_from: could not find useable envelope sender
Is there any way that I can tell SpamAssassin to trust the
X-Envelope-From or Return-Path information in the headers as it is
merely an AV gateway and not going to change the X-Envelope-From headers?
This way I could get SPF checks on the senders as well as be able to use
SPF Whitelist From.
Thanks
Ben
