| Port details on branch 2022Q2 |
- py-spf-engine SPF engine for Postfix policy server and milter implemented in Python
- 3.0.4 mail
 =2      3.0.4Version of this port present on the latest quarterly branch. - Maintainer: yasu@FreeBSD.org
- Port Added: 2020-05-31 13:49:34
- Last Update: 2023-06-27 19:34:34
- Commit Hash: 3d9a815
- People watching this port, also watch:: p5-Net-HTTP, json-c, python, py39-pycparser, tmux
- Also Listed In: python
- License: APACHE20 GPLv2+
- WWW:
- https://launchpad.net/spf-engine
- Description:
- This project provides the SPF (Sender Policy Framework) back-end for both
pypolicyd-spf (for which it was originally developed) and an future SPF
milter using pymilter. The goal is to provide a common back-end for common
features for support SPF integration with Postfix and Sendmail using both
the Postfix policy service and the Sendmail milter protocol (also available
with Postfix).
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}spf-engine>0:mail/py-spf-engine@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/mail/py-spf-engine/ && make install clean
- To add the package, run one of these commands:
- pkg install mail/py-spf-engine
- pkg install py39-spf-engine
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py39-spf-engine listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py39-spf-engine
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1681795743
SHA256 (spf-engine-3.0.4.tar.gz) = 19cc3b7a73486ff4eb64461ad19d387b31d499f32673527e6841fa1655db853a
SIZE (spf-engine-3.0.4.tar.gz) = 61428
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py39-flit-core>=3.8<4 : devel/py-flit-core@py39
- python3.9 : lang/python39
- py39-build>=0 : devel/py-build@py39
- py39-installer>=0 : devel/py-installer@py39
- Test dependencies:
-
- python3.9 : lang/python39
- Runtime dependencies:
-
- py39-authres>0 : mail/py-authres@py39
- py39-milter>0 : mail/py-milter@py39
- py39-pyspf>0 : mail/py-pyspf@py39
- python3.9 : lang/python39
- There are no ports dependent upon this port
Configuration Options:- ===> The following configuration options are available for py39-spf-engine-3.0.4:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
- Options name:
- mail_py-spf-engine
- USES:
- python shebangfix
- pkg-message:
- For install:
- #
# Using policyd-spf with Postfix
#
Policyd-spf must be integrated with Postfix to be effective:
1. Add to your postfix master.cf:
policyd-spf unix - n n - 0 spawn
user=nobody argv=/usr/local/bin/policyd-spf
2. Configure the Postfix policy service in your main.cf so that the
"smtpd_recipient_restrictions" includes a call to the policyd-spf policy
filter. If you already have a "smtpd_recipient_restrictions" line, you can
add the "check_policy_service" command anywhere *after* the line which
reads "reject_unauth_destination" (otherwise you're system can become an
open relay).
smtpd_recipient_restrictions =
...
reject_unauth_destination
check_policy_service unix:private/policyd-spf
...
policyd-spf_time_limit = 3600
3. Please consult the postfix documentation for more information on these and
other settings you may wish to have in the "smtpd_recipient_restrictions"
configuration.
4. Reload postfix.
#
# Automatically starting pyspf-milter at boot time.
#
Add 'pyspf_milter_enable="YES"' to /etc/rc.conf.
#
# Using pyspf-milter with Sendmail
#
Following is an example configuration line to include in your sendmail.mc.
INPUT_MAIL_FILTER(`pyspf-milter', `S=local:/var/run/pyspf-milter/pyspf-milter.sock')dnl
#
# Using pyspf-milter with Postfix
#
Integration of pyspf-milter into Postfix is like any milter (See Postfix's
README_FILES/MILTER_README). But care is required to segregate outbound mail
from inbound mail to be checked. Here is example using milter macros to keep
the mail streams segregated.
/usr/local/etc/postfix/main.cf:
smtpd_milters = unix:/var/run/pyspf-milter/pyspf-milter.sock
/usr/local/etc/postfix/master.cf:
smtp inet n - - - - smtpd
...
-o milter_macro_daemon_name=VERIFYING
...
/usr/local/etc/python-policyd-spf/policyd-spf.conf:
MacroList daemon_name|VERIFYING
- Master Sites:
|
As an Amazon Associate I earn from qualifying purchases.