Re: Exim 4.41 + Exiscan 4.41-24 + libspf2 1.0.4

Well, we found out what was happening.

Any connection that simply doesn't specify a syntactically correct 
"helo/ehlo" domain will cause Exiscan's SPF to return error_temp (5).  
One reason is:

int spf_init(uschar *spf_helo_domain, uschar *spf_remote_addr) {

It looks like we'll have to force a valid HELO first.

Someone should put a note in the Exiscan docs that a HELO is required 
for SPF.

Rich
[email protected]

On Monday, July 26, 2004, at 02:54 PM, Rich, WhidbeyNET NOC wrote:

> We've been using Exiscan for a while under Exim 4.30.  During our 
> upgrade cycle to 4.41, we thought we'd try to implement SPF.
>
> After installing libspf2 1.0.4, we tried to compile Exim 4.41 with the 
> latest Exiscan 4.41-24 patch, with the following in the Makefile:
>
> CFLAGS=-DSPF -I/usr/local/include
> EXTRALIBS_EXIM=-L/usr/local/lib -lpam -lspf2
> WITH_SPF=yes
>
> The only compile error was in "spf.h", for these 3 includes:
>
> #include <spf_alt/spf.h>
> #include <spf_alt/spf_dns_resolv.h>
> #include <spf_alt/spf_dns_cache.h>
>
> It looks like they weren't renamed to "spf2/" when libspf changed its 
> name, so we changed them, and it compiled file.
>
> However we cannot get any SPF lookup to complete in Exim. Here's an 
> example test ACL:
>
> acl_check_mail:
>         deny    spf = !fail
>                 message = SPF: $spf_header_comment Comment: 
> $spf_smtp_comment
>
> It only generates this in exim -bd -d:
>
>  2488 SMTP<< mail from:[email protected]
>  2488 using ACL "acl_check_mail"
>  2488 processing "deny"
>  2488 check spf = !fail
>  2488 SPF result is error (5)
>  2488 deny: condition test succeeded
>  2488 SMTP>> 550 SPF:  Comment:
>  2488 LOG: MAIN REJECT
>  2488   H=[209.166.64.90] rejected MAIL [email protected]: SPF:  
> Comment:
>  2488 SMTP<< QUIT
>
> The only thing being returned is "error_temp" (5). Since there is 
> nothing being returned for any spf return values we've tried, we are 
> having trouble isolating the problem.
>
> The "spfquery" command-line tool functions just fine:
>
> ./spfquery -ip=209.166.64.124 [email protected]
> pass
> spfquery: domain of whidbey.net designates 209.166.64.124 as permitted 
> sender
>
> We also tried removing, and then installing lower versions, of libspf2 
> with no success.
>
> Can anyone suggest some better debugging methods, short of going 
> through Exim and the SPF code to insert breakpoints?
>
> Thanks!
>
> Rich
> [email protected]
>