You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm setting up a new personal email server running Ubuntu 22.10 and just implemented postgrey using the available Ubuntu package.
The logs emitted by postgrey are landing in /var/log/syslog, instead of /var/log/mail.log where I expect them to be.
These are the logs I see in /var/log/syslog when I sudo service postgrey start the daemon.
Feb 25 14:03:29 polar systemd[1]: Started Postfix greylisting policy server.
Feb 25 14:03:29 polar postgrey[45397]: 2023/02/25-14:03:29 postgrey (type Net::Server::Multiplex) starting! pid(45397)
Feb 25 14:03:29 polar postgrey[45397]: Resolved [localhost]:10023 to [::1]:10023, IPv6
Feb 25 14:03:29 polar postgrey[45397]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
Feb 25 14:03:29 polar postgrey[45397]: Binding to TCP port 10023 on host ::1 with IPv6
Feb 25 14:03:29 polar postgrey[45397]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4
Feb 25 14:03:29 polar postgrey[45397]: Setting gid to "999 999"
Feb 25 14:03:29 polar postgrey[45397]: Setting uid to "998"
I tried figuring out what's going on, but everything looks OK to me with my very rusty Perl skills. Not sure why the syslog_facility isn't being set on the syslog connection properly.
The text was updated successfully, but these errors were encountered:
I'm setting up a new personal email server running Ubuntu 22.10 and just implemented postgrey using the available Ubuntu package.
The logs emitted by postgrey are landing in /var/log/syslog, instead of /var/log/mail.log where I expect them to be.
These are the logs I see in /var/log/syslog when I
sudo service postgrey start
the daemon.I tried figuring out what's going on, but everything looks OK to me with my very rusty Perl skills. Not sure why the
syslog_facility
isn't being set on the syslog connection properly.The text was updated successfully, but these errors were encountered: