python 3.x compatibility issue

It's 2.0.7 with some patches (roughly equivalent to what's in CVS). Perhaps more importantly it's py3dns 3.0.2 and it did have an incompatible change from 3.0.1.

There is a known issue (as of yesterday) with IPv6 processing in pyspf on python 3 that I'm still trying to figure out.

I have figured out the issue I mentioned in the last comment.

If you look at http://anonscm.debian.org/viewvc/python-modules/packages/pyspf/tags/2.0.7-4/debian/patches/ you can see the two patches I've applied to pyspf for Debian/Ubuntu (including fixing the most recent issue).

I did go back and look and I'm pretty sure py3dns 3.0.1 won't work, you need 3.0.2 because of some incompatibilities between the two.

pyspf 2.0.8 was just released that solves the python3.2 problems. It did, however, drop a function I was using in this package, so I need to release an update, which I will do shortly. py3dns 3.0.3, pyspf 2.0.8, and pypolicyd-spf 1.2 (not yet released) will solve this without any patching needed.

1.2 is released. In combination with pyspf 2.0.8 it should work fine now.

I'm still seeing the first of these errors after adding official python-3.x support to policyd-spf in Gentoo. We've got,

  * policyd-spf-1.2
  * pyspf-2.0.9
  * pydns-3.0.2
  * python-3.3.x or python-3.4.x

The machine on which I reproduced the error has python-3.3 built with python ipv6 support, but ipv6 disabled in the kernel. Below are the logs for one of the failed transactions.

May 10 00:19:10 mx1 postfix/smtpd[16219]: connect from smtprelay130c.careerbuilder.com[208.82.4.175]
May 10 00:19:10 mx1 postfix/smtpd[16219]: discarding EHLO keywords: DSN
May 10 00:19:10 mx1 policyd-spf[1301]: Starting
May 10 00:19:10 mx1 policyd-spf[1301]: Config: {'Mail_From_reject': 'Fail', 'Header_Type': 'SPF', 'debugLevel': 3, 'Mail_From_pass_restriction': 'spf_pass_from', 'defaultSeedOnly': 1, 'PermError_reject': 'False', 'skip_addresses': '127.0.0.0/8,::ffff:127.0.0.0/104,::1', 'Reject_Not_Pass_Domains': 'aexp.com,aim.com,aol.com,apple.com,dhl.com,gmail.com,googlemail.com,hallmark.com,hotmail.com,linkedin.com,live.com,msn.com,paypal.com,e.paypal.com,verizon.net', 'HELO_reject': 'Fail', 'TempError_Defer': 'False', 'HELO_pass_restriction': 'spf_pass_helo'}
May 10 00:19:10 mx1 policyd-spf[1301]: spfcheck: pyspf result: "['None', '', 'helo']"
May 10 00:19:10 mx1 policyd-spf[1301]: None; identity=helo; client-ip=208.82.4.175; helo=smtprelay130c.careerbuilder.com; <email address hidden>; <email address hidden>
May 10 00:19:10 mx1 policyd-spf[1301]: Traceback (most recent call last):
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib64/python3.3/site-packages/DNS/Base.py", line 192, in getSource
May 10 00:19:10 mx1 policyd-spf[1301]: self.s.bind(('', source_port))
May 10 00:19:10 mx1 policyd-spf[1301]: OSError: [Errno 98] Address already in use
May 10 00:19:10 mx1 policyd-spf[1301]:
May 10 00:19:10 mx1 policyd-spf[1301]: During handling of the above exception, another exception occurred:
May 10 00:19:10 mx1 policyd-spf[1301]: Traceback (most recent call last):
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib/python-exec/python3.3/policyd-spf", line 662, in <module>
May 10 00:19:10 mx1 policyd-spf[1301]: instance_dict, configData, peruser)
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib/python-exec/python3.3/policyd-spf", line 508, in _spfcheck
May 10 00:19:10 mx1 policyd-spf[1301]: res = spf.check2(ip, sender, helo)
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib64/python3.3/site-packages/spf.py", line 310, in check2
May 10 00:19:10 mx1 policyd-spf[1301]: receiver=receiver,timeout=timeout,verbose=verbose,querytime=querytime).check()
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib64/python3.3/site-packages/spf.py", line 555, in check
May 10 00:19:10 mx1 policyd-spf[1301]: spf = self.dns_spf(self.d)
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib64/python3.3/site-packages/spf.py", line 1120, in dns_spf
May 10 00:19:10 mx1 policyd-spf[1301]: a = [t for t in self.dns_txt(domain) if RE_SPF.match(t)]
May 10 00:19:10 mx1 policyd-spf[1301]: File "/usr/lib64/python3.3/site-packages/spf.py", line 1169, in dns_txt
May 10 00:19:10 mx1 policyd-spf[1301]: dns_list =...

I have occasionally seen this error as well:

May 10 00:19:10 mx1 policyd-spf[1301]: self.s.bind(('', source_port))
May 10 00:19:10 mx1 policyd-spf[1301]: OSError: [Errno 98] Address already in use

This is a py3dns/pydns error, not an error in pypolicyd-spf. I'll have a look at fixing it there.

Additionally, I just release pypolicyd-1.3 yesterday and once you have that with pyspf 2.0.9 you have an SPF system that's fully updated for the new SPF RFC, RFC 7208.

This is fixed in py3dns 3.1.0 (you have 3.0.2). Here's the commit that fixed it:

http://bazaar.launchpad.net/~py3dns-hackers/py3dns/trunk/revision/121

Great, thanks. It looks like we missed the py3dns move to Launchpad and fell a few versions behind as a result. I'll get that fixed and require a newer pydns when I bump pypolicyd-spf.

I'm still getting these:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.3/policyd-spf", line 680, in <module>
    instance_dict, configData, peruser)
  File "/usr/lib/python-exec/python3.3/policyd-spf", line 407, in _spfcheck
    foo = string.split(sender, '@', 1)
AttributeError: 'module' object has no attribute 'split'

Installed versions:

python 3.3
pyspf 2.0.9
pydns 3.1.0
pypolicyd-spf 1.3.1

I think replacing line 407 from this:

foo = string.split(sender,'@',1)

to this:

foo = sender.split('@',1)

would fix the problem

Thanks, that's quite correct and I've fixed it for the next release.

More interesting (for me anyway) is why my test suite didn't catch it. I've fixed that as well.

Fixed in 1.3.2 https://pypi.python.org/pypi/pypolicyd-spf/1.3.2