How to use Sender Policy Framework on Debian Server

Sender Policy Framework (SPF) is a service deployed to avoid being identified as a spam sender.

postfix-policyd-spf is a fully functional engine for SPF verification under Postfix. The daemon includes a variety of mechanisms and policy options to meet a wide variety of system requirements. postfix-policyd-spf-perl was implemented on Perl, further on Python there is postfix-policyd-spf-python, the Python SPF module (spf) is used. As a Postfix module, it supports RFC 7208 of the Sender Policy Framework (SPF).

How to use Sender Policy Framework on Debian Server

Additional information is stored in the DNS (Domain Name System) in the form of an SPF record. This TXT-based SPF record contains specific information about authorized mail servers, Mail Transfer Agent (MTA).

How to install Postfix policyd-spf

The installation on Debian 10 and Debian 11 starts as root as follows:

$ apt install postfix-policyd-spf-python

If the Perl module is preferred, the Perl SPF-Milter can be installed as root as follows.

$ apt install postfix-policyd-spf-perl

After postfix-policyd-spf-python, or postfix-policyd-spf-perl is installed, we edit the configuration file of the postfix master process.

$ vi /etc/postfix/

To launch the Postfix statement with the Python SPF policy checker, add the following lines to the end of the file.

policyd-spf  unix  -       n       n       -       0       spawn
   user=policyd-spf argv=/usr/bin/policyd-spf

Use the SPF policy verification on the Perl implementation is as follows.

policyd-spf  unix  -       n       n       -       0       spawn
   user=policyd-spf argv=/usr/sbin/postfix-policyd-spf-perl

Save and close the file. Next, edit the Postfix main configuration file.

$ vi /etc/postfix/

Add the following lines to the end of the file. The first line specifies the timeout setting for the Postfix Policy Agent. The following lines restrict incoming emails by checking the SPF record and rejecting unauthorized emails.

policyd-spf_time_limit = 3600
smtpd_recipient_restrictions =
   check_policy_service unix:private/policyd-spf

Note! if check_policy_service is not the last line below the section smtpd_recipient_restrictions, then there must be a comma (,) at the end of the line. No comma on the last entry.

Save and close the file.

  Ensure that the user id policyd-spf exist by run id policyd-spf, if not exist, the system account is created as follows.

$ useradd -r -M policyd-spf -s /usr/sbin/nologin

Then restart the Postfix using systemctl.

$ systemctl restart postfix

The next time receive an email by a domain with an SPF record in DNS, you can see the results of the SPF verification in the RAW email header. The following header indicates that the sender sent the email from an authorized host.

policyd-spf[733750]: prepend Received-SPF: Pass

The output appers when using Postfix Policy-SPF with Perl.

postfix/policy-spf[735983]: Policy action=PREPEND Received-SPF: pass

Verify Python and SPF

When using postfix-policyd-spf-python, Python must be available on the server, as well as the Python SPF module. The verification can be carried out as follows.

$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> help('modules')

If Python is installed on the system, the help('modules') command displays multiple modules in columns. The spf and spf_engine module is required. The Python module can be added as follows.

pip install pypolicyd-spf

Verify SPF Record

To verify the SPF TXT Record for a specific domain, run the lookup command out from linux terminal.

$ dig TXT +short
 "v=spf1 a mx ~all"

Using windows then run this command in the command prompt (cmd).

C:\> nslookup -type=TXT
 "v=spf1 a mx ~all"

Launch OpenVPN connection from KeePass

If you use the KeePass Password Manager for system administration, it makes sense to launch the connection and authentication directly from KeePass, for this purpose the user and password can be transferred via variables to another program, such as an FTP client or a browser. It would also be practical if you could launch a VPN tunnel directly from KeePass.

This tutorial shows how to set up and launch a VPN connection from KeePass using the OpenVPN GUI.

Start KeePass OpenVPN connection

In which a new entry is created in KeePass, we add the target gateway to User name, namely the file name of the .ovpn connection file, which is created in the OpenVPN GUI, for connection to a VPN router or to a firewall.

cmd://"C:\Program Files\OpenVPN\bin\openvpn-gui.exe" --config_dir %USERPROFILE%\OpenVPN\config\ --connect {USERNAME}

Insert the line in the URL field, the paths correspond to those provided during the installation of the OpenVPN GUI Setup. If different directory paths are used, they must be adjusted.

The VPN connection is now started in the KeePass overview with a double click on the URL line, or with hit the key Ctrl+U.