Dear Maintainer,

   * What led up to the situation?

Installed postgrey from core Debian repos and configured it to run with postfix. I monitor it with monit. Up until Bookworm it seemed to run fine. Now it doesn't seem to create a PID file, which prevents monit from monitoring it. I suspect this is related to #756813 and #934068.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I tried creating the directory /run/postgrey, chowning it to belong to the postgrey user, and adding this line to /etc/default/postgrey:

PIDFILE=/run/$DAEMON_NAME/$DAEMON_NAME.pid

   * What was the outcome of this action?

It made no difference. In /etc/init.d/postgrey, the --pidfile option is included before loading /etc/default/postgrey, so I hoped it would pick up the overridden value. In practice, `ps aux` shows that the --pidfile option isn't being used by the postgrey process. Additionally, I believe that /run/postgrey does not persist across reboots.

   * What outcome did you expect instead?

Since the problem seems to be related to permissions (although I haven't been able to find any confirmation in my logs), I hoped that putting the pid file in a directory owned by the postgrey user would get around that problem. Although I suspect that the