On Sun, 12 Feb 2012, email builder wrote:

On 02/10, email builder wrote:
 > I believe for SPF you *should* be doing the detecting at your MTA
 > (mail server software) and inserting a header for spamassassin to use:
> Received-SPF.  (Because SPF is supposed to use the "envelope > from",
 > which is not necessarily included in a header.)

I see. That makes sense. Is there a wiki page suggesting solutions for this? Anyone know of tips for doing this in postfix? Or during amavis processing?

I use postfix-policyd-spf-perl.
Which appears to currently be officially hosted at:
https://launchpad.net/postfix-policyd-spf-perl/

Thanks for that, although see my last post - do you know if the SPF tests only 
know how to look for that Received-SPF header or can use the envelope sender if 
it's present?

If your MTA provides sufficient info for SA to determine the envelope sender that is enough. I've been using sendmail+milter+sa for years with SPF & DKIM rules and never had any kind of special MTA added 'Received-SPF' header.

One thing that -is- a factor; sa depends upon specific perl modules
for that functionality; DNS, SPF, & DKIM modules (EG Net::DNS, Mail::DKIM, Mail::SPF ), and 'loadplugin' statements in the correct ".pre" files.
Occasionally issues arise with problematic versions of those modules.
For example, search this list archive for disussions about problems caused by buggy versions of the DNS module.

If you execute the test:
  % spamassassin --lint -D 2>&1 | grep -i -E 'spf|dkim|dns'

You should see output that looks something like:

Feb 12 20:08:05.530 [13365] dbg: dns: is Net::DNS::Resolver available? yes
Feb 12 20:08:05.530 [13365] dbg: dns: Net::DNS version: 0.63
Feb 12 20:08:06.394 [13365] dbg: diag: [...] module installed: Net::DNS, 
version 0.63
Feb 12 20:08:06.394 [13365] dbg: diag: [...] module installed: Mail::SPF, 
version v2.007
Feb 12 20:08:06.395 [13365] dbg: diag: [...] module installed: Mail::DKIM, 
version 0.39
Feb 12 20:08:06.409 [13365] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::URIDNSBL from @INC
Feb 12 20:08:06.414 [13365] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::SPF from @INC
Feb 12 20:08:06.429 [13365] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::DKIM from @INC
Feb 12 20:08:06.446 [13365] dbg: plugin: loading 
Mail::SpamAssassin::Plugin::DNSEval from @INC
[snip ...]

If you don't see those 'plugin: loading' lines for SPF & DKIM, then there's your problem. Either they're not installed on your system in a way that SA can find them, wrong verions, or not invoked by 'loadplugin' statements.

--
Dave Funk                                  University of Iowa
<dbfunk (at) engineering.uiowa.edu>        College of Engineering
319/335-5751   FAX: 319/384-0549           1256 Seamans Center
Sys_admin/Postmaster/cell_admin            Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{

Reply via email to