Found what the problem was. Turns out spamd was running by default with the -L (Use local tests only (no DNS)) parameter. Removed this and restarted de daemon and voila:
Jun 24 21:21:21 higis-s3 spamd[22778]: spamd: connection from localhost [::1]:36303 to port 783, fd 5 Jun 24 21:21:21 higis-s3 spamd[22778]: spamd: setuid to vscan succeeded Jun 24 21:21:21 higis-s3 spamd[22778]: spamd: processing message <CAD14S=F61WBUWit_s_eFEA--0p=yabzvwxysoo2phepsj6c...@mail.gmail.com> for vscan:65 Jun 24 21:21:22 higis-s3 spamd[22778]: spamd: clean message (-2.1/5.0) for vscan:65 in 1.2 seconds, 2487 bytes. Jun 24 21:21:22 higis-s3 spamd[22778]: spamd: result: . -2 - *DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VERIFIED*,HTML_MESSAGE,LOCAL_SPF_PASS,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL scantime=1.2,size=2487,user=vscan,uid=65,required_score=5.0,rhost=localhost,raddr=::1,rport=36303,mid=<CAD14S=F61WBUWit_s_eFEA--0p=yabzvwxysoo2phepsj6c...@mail.gmail.com>,autolearn=ham autolearn_force=no Jun 24 21:21:22 higis-s3 spamd[22776]: prefork: child states: II On 06/24/2016 08:40 PM, Benny Pedersen wrote: > On 2016-06-24 20:22, G.H. (Spamassassin) wrote: > >>> I notice that the DNS whitelisting rules are missing too, and the SPF >>> rules are replaced by a custom rule LOCAL_SPF_PASS. >> >> Correct, I made few SPF rules of my own but that could be the cause I >> believe? > > i see no spf pass ever here with spamassassin active spf test, but > seem that spf helo pass works, just not spf testing on envelope sender > > so it could very well be common dns problems > >>> Is it possible that spamd is having a problem with DNS access? >>> Something that doesn't affect the command line and whatever is adding >>> Received-SPF. >>> >> I'll check this.out. > > yes will here aswell, it breaked here when i dropped pypolicyd-spf, > will see if i can revert this in working order
