EPEL Maintainers,
It appears the update to pypolicyd-spf-2.9.3 from pypolicyd-spf-2.0.x crashes Postfix unexpectedly. Perhaps a missing dependency? Seems to be ahead from what I assume the upstream is, pip. Is this an error? Installing authres via pip was able to fix things without installing pypolicyd-spf via pip.
Below is what I got with the new version:
Nov 14 22:03:15 mail postfix/smtpd[8311]: send attr policy_context = Nov 14 22:03:15 mail postfix/smtpd[8311]: private/policyd-spf: wanted attribute: action ... Nov 14 22:03:15 mail postfix/smtpd[8311]: private/policyd-spf: wanted attribute: action Nov 14 22:03:15 mail postfix/smtpd[8311]: input attribute name: File "/usr/lib/python3.9/site-packages/spf_engine/__init__.py", line 54, in <module> Nov 14 22:03:15 mail postfix/smtpd[8311]: private/policyd-spf: wanted attribute: action Nov 14 22:03:15 mail postfix/smtpd[8311]: input attribute name: import authres Nov 14 22:03:15 mail postfix/smtpd[8311]: private/policyd-spf: wanted attribute: action Nov 14 22:03:15 mail postfix/smtpd[8311]: input attribute name: ModuleNotFoundError: No module named 'authres' Nov 14 22:03:15 mail postfix/smtpd[8311]: private/policyd-spf: wanted attribute: action Nov 14 22:03:15 mail postfix/spawn[8318]: warning: command /usr/libexec/postfix/policyd-spf exit status 1 Nov 14 22:03:15 mail postfix/smtpd[8311]: warning: premature end-of-input on private/policyd-spf while reading input attribute name Nov 14 22:03:15 mail postfix/smtpd[8311]: warning: problem talking to server private/policyd-spf: Connection reset by peer Nov 14 22:03:16 mail postfix/postfix-script[8364]: stopping the Postfix mail system
- Thanks, Sylvain
Hi,
Sylvain Jones via epel-devel wrote:
It appears the update to pypolicyd-spf-2.9.3 from pypolicyd-spf-2.0.x crashes Postfix unexpectedly. Perhaps a missing dependency?
It looks like pypolicyd-spf-2.9.3-2 should be in epel-testing now. That update will install python3-authres, so you may way to clean up the pip-installed copy you mention below.
https://bugzilla.redhat.com/show_bug.cgi?id=2142476
Seems to be ahead from what I assume the upstream is, pip. Is this an error? Installing authres via pip was able to fix things without installing pypolicyd-spf via pip.
The upstream project was renamed some time ago. It is now called spf-engine, which is at 2.9.3 in pypi as well.
https://bugzilla.redhat.com/show_bug.cgi?id=1801011
Once upon a time, Todd Zullinger tmz@pobox.com said:
Sylvain Jones via epel-devel wrote:
It appears the update to pypolicyd-spf-2.9.3 from pypolicyd-spf-2.0.x crashes Postfix unexpectedly. Perhaps a missing dependency?
It looks like pypolicyd-spf-2.9.3-2 should be in epel-testing now. That update will install python3-authres, so you may way to clean up the pip-installed copy you mention below.
Except... for EPEL 9, there is no python3-authres. There is a request for it to be added though:
https://bugzilla.redhat.com/show_bug.cgi?id=2142503
Chris Adams wrote:
Once upon a time, Todd Zullinger tmz@pobox.com said:
Sylvain Jones via epel-devel wrote:
It appears the update to pypolicyd-spf-2.9.3 from pypolicyd-spf-2.0.x crashes Postfix unexpectedly. Perhaps a missing dependency?
It looks like pypolicyd-spf-2.9.3-2 should be in epel-testing now. That update will install python3-authres, so you may way to clean up the pip-installed copy you mention below.
Except... for EPEL 9, there is no python3-authres. There is a request for it to be added though:
Oops. Looks like there's a similar issue for python3-pymilter which was added as another missing dependency in the -3 package, per:
https://bugzilla.redhat.com/2142743
A bug was filed to branch pymilter for EPEL-9 in August and a duplicate was filed today:
https://bugzilla.redhat.com/2120091 https://bugzilla.redhat.com/2142747
epel-devel@lists.fedoraproject.org