Package: postgrey Version: 1.35-1 Severity: normal Apr 17 17:28:29 itmustbe postgrey[5491]: Resolved [localhost]:10023 to [::1]:10023, IPv6 Apr 17 17:28:29 itmustbe postgrey[5491]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4 Apr 17 17:28:29 itmustbe postgrey[5491]: Binding to TCP port 10023 on host ::1 with IPv6
On startup I see messages like the above and then postgrey is not running. It turns out that SE Linux is preventing postgrey from binding to port 10023, but the same result could happen from using any of the other advanced security systems on Linux or by just running as non-root and using a port below 1024 (which might be unusual but probably someone wants to do it). Postgrey should not just silently die. It should log a message to syslog explaining the problem before exiting. -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgrey depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libberkeleydb-perl 0.54-2+b1 ii libnet-dns-perl 0.81-2 ii libnet-server-perl 2.008-1 ii perl 5.20.2-3+deb8u4 ii ucf 3.0030 Versions of packages postgrey recommends: pn libnet-rblclient-perl <none> pn libparse-syslog-perl <none> ii postfix 2.11.3-1 postgrey suggests no packages. -- debconf information: postgrey/1.32-3_changeport:
