Bug 2159114

+++ This bug was initially created as a clone of Bug #1848574 +++

Postgrey recently installed and keeps complaining:

Jun 18 10:30:10 myhost systemd[1]: /usr/lib/systemd/system/postgrey.service:10: PIDFile= references a path below legacy directory /var/run/, updating /var/run/postgrey.pid → /run/postgrey.pid; please update the unit file accordingly.

--- Additional comment from  on 2020-10-28 20:17:10 UTC ---

Also, should add:

After=network.target

Otherwise, postgrey attempts to start before the network and fails, causing a retry.  Starting after the network is cleaner.  Verified on FC33.

--- Additional comment from  on 2021-06-10 11:31:15 UTC ---

Running on FC34 now with:

After=network-online.target

--- Additional comment from Anthony Messina on 2021-11-07 19:38:01 UTC ---

Confirmed this issue is still present in Fedora 35.

I am using the following systemd service unit instead of the packaged default.  Type=forking is not required and the user/group can be set in the unit file itself.


[Unit]
Description=Postfix Greylisting Service
Documentation=man:postgrey(8)
After=network-online.target
Before=postfix.service

[Service]
Type=simple
User=postgrey
ExecStart=/usr/sbin/postgrey \
 --unix=/var/spool/postfix/postgrey/socket \
 --greylist-text='Greylisted for %%s seconds' \
 --delay=60

Restart=always
RestartSec=1
TimeoutSec=5

[Install]
WantedBy=multi-user.target

--- Additional comment from Anthony Messina on 2022-11-20 14:14:53 UTC ---

This is still present in F37.

--- Additional comment from Ben Cotton on 2022-11-29 16:48:55 UTC ---

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

--- Additional comment from Anthony Messina on 2022-11-29 17:12:03 UTC ---

Dad are you able to update the version to Rawhide?

--- Additional comment from Ben Cotton on 2022-12-13 15:15:21 UTC ---

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.