Package Details: python-pyspf 2.0.14-2

Git Clone URL: (read-only, click to copy)
Package Base: python-pyspf
Description: Python implementation of the Sender Policy Framework (SPF) protocol
Upstream URL:
Licenses: PSF
Submitter: ras0ir
Maintainer: qft
Last Packager: qft
Votes: 11
Popularity: 0.001078
First Submitted: 2009-04-21 17:45
Last Updated: 2020-12-04 17:12

Latest Comments

1 2 Next › Last »

corruption2013 commented on 2019-12-14 02:27

This package is broken! Because of the issue described here:

It only occurs with some mail providers....

Please fix it.

My solution was to downgrade to 2.0.12 for now...

pezz commented on 2019-11-25 10:38

This broke for me, changing the line as per this fixed it:

crt commented on 2018-08-08 01:33

FWIW, I had to manually specify the python3.7 binary otherwise python-pyspf kept installing to /usr/lib/python3.6 unexpectedly.

crt commented on 2018-08-07 01:01

Today I upgraded python (3.6.6-1 -> 3.7.0-3) and other packages that depend on PyDNS are failing because python cannot import 'spf'.

$ /usr/bin/policyd-spf
Traceback (most recent call last):
  File "/usr/bin/policyd-spf", line 39, in <module>
    import spf
ModuleNotFoundError: No module named 'spf'
Python 3.7.0 (default, Jul 15 2018, 10:44:58)
[GCC 8.1.1 20180531] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import spf
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'spf

richli commented on 2015-09-04 19:20

My email bounced (funny how an email-oriented package does not have the maintainers' email address working), but upstream released a fix, so now 2.0.12 is available.

richli commented on 2015-08-10 21:25

Although version 2.0.12 is out, it is completely broken due to using tab-indentation for a few lines. Therefore the script will not run in Python 3. The indentation is ambiguous, so that I cannot correct it myself. I sent an email to on 2015-08-10 to notify them of the issue.

Until upstream fixes the release, I've downgraded the package back to 2.0.11.

richli commented on 2015-08-10 20:52

@fauno: oh, I was wrong, it's not a warning, it's a full-blown error. That's pretty egregious for upstream to release this. I'll check into it more.

richli commented on 2015-08-06 17:55

@fauno: yeah, I noticed that too, but it just looks like a warning. Upstream should fix this, but a one-liner sed command would fix it too. When I get some time later, I'll try to fix it. Or if you figure it out and post it here, I can update the package sooner. :)

fauno commented on 2015-08-06 16:27


lines 845 and 1941

fauno commented on 2015-08-06 16:27

there's a file with mixed tabs and spaces and python complains until you fix them