Hide Forgot
Description of problem: Apr 3 07:17:57 examplesrv policyd-spf[11516]: Traceback (most recent call last): Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/libexec/postfix/policyd-spf", line 680, in <module> Apr 3 07:17:57 examplesrv policyd-spf[11516]: instance_dict, configData, peruser) Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/libexec/postfix/policyd-spf", line 517, in _spfcheck Apr 3 07:17:57 examplesrv policyd-spf[11516]: res = spf.check2(ip, sender, helo, querytime=configData.get('Lookup_Time')) Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 297, in check2 Apr 3 07:17:57 examplesrv policyd-spf[11516]: receiver=receiver,timeout=timeout,verbose=verbose,querytime=querytime).check() Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 547, in check Apr 3 07:17:57 examplesrv policyd-spf[11516]: rc = self.check1(spf, self.d, 0) Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 586, in check1 Apr 3 07:17:57 examplesrv policyd-spf[11516]: return self.check0(spf, recursion) Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 900, in check0 Apr 3 07:17:57 examplesrv policyd-spf[11516]: if self.cidrmatch(self.dns_mx(arg), cidrlength): Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 1194, in dns_mx Apr 3 07:17:57 examplesrv policyd-spf[11516]: return [a for mx in mxnames[:max] for a in self.dns_a(mx[1],self.A)] Apr 3 07:17:57 examplesrv policyd-spf[11516]: File "/usr/lib/python2.7/site-packages/spf.py", line 1206, in dns_a Apr 3 07:17:57 examplesrv policyd-spf[11516]: return [ipaddress.Bytes(ip) for ip in r] Apr 3 07:17:57 examplesrv policyd-spf[11516]: AttributeError: 'module' object has no attribute 'Bytes' Version-Release number of selected component (if applicable): python-ipaddr-2.1.9-5.el7.noarch
Why is this version 7.5-Pegas rather 7.4? Could you adjust it, please? Cross-filed case 01781715 on the Red Hat customer portal.
*** Bug 1208811 has been marked as a duplicate of this bug. ***
*** Bug 1400694 has been marked as a duplicate of this bug. ***
Hi, is there any estimate when this will be moved from QA to production?
(In reply to Liam Middlebrook from comment #9) > Hi, is there any estimate when this will be moved from QA to production? Hello Liam, Unfortunately we cannot provide an estimate currently, of when this fix will be deployed to production.
Liam, it will be rather months than weeks, but feel free to contact the RH Customer Support for some better answer, because engineering is not able to provide such information. Thanks for understanding.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1925