Hi, I triaged this bug on a fresh stretch VM. Installing postgrey 1.36-3 and rebooting did not trigger the bug. I tried with both systemd and sysvinit. Looking at /etc/init.d/postgrey, I see the following:
PIDFILE=/var/run/$DAEMON_NAME.pid So the above init script shipped in stretch does not require /var/run/postgrey/ to be created, since it is not used. But wait! Since the init script is a conffile, it could be that the reporter upgraded from jessie. However, postgrey 1.35-1 also has the following line: PIDFILE=/var/run/$DAEMON_NAME.pid As such, I don't think this bug ever existed in stretch or jessie, but was a result of users trying to fix #756813. It may be possible that the init script was inherited from wheezy or earlier, I did not check those releases. If that was the case, I think the bug would have been noticed earlier. Greetings from the Chemnitz BSP, Lee
