<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I have been wrestling with postfix logging. <div class=""><br class=""></div><div class="">The weird thing was that I did not see any logging from smtp/smtpd/postscreen, but I did see logging from qmgr and some others. But, when I created an error in main.cf (e.g. a file that doesn’t exist), I did see logging.</div><div class=""><br class=""></div><div class="">The outcome of this (with help from Wietse) is that the following happens: when you run smtpd/smtp/postscreen in a chroot jail, the daemons cannot open the socket to postlogd. So, there is no logging from those. But, when you force an error in main.cf, the error is reported before dropping privileges/chroot so it is seen.</div><div class=""><br class=""></div><div class="">So, for now, if you want logging from smtpd/smtp of postfix via postlogd (syslog is out of the question anyway given how broken macOS is on that front), you need to not run it in a chroot jail.</div><div class=""><br class=""></div><div class="">Wietse will adapt the code of postfix so in an upcoming update, the socket to postlogd will be opened before dropping privileges.</div><div class=""><br class=""></div><div class="">I wonder if everybody sees this (no smtpd logging to postlogd) of if there is some special situation on my machine that triggers this.</div><div class=""><br class=""><div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Gerben Wierda</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="http://enterprisechess.com/" class="">Chess and the Art of Enterprise Architecture</a></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="http://masteringarchimate.com/" class="">Mastering ArchiMate</a></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="https://www.infoworld.com/blog/architecture-for-real-enterprises/" class="">Architecture for Real Enterprises</a> at InfoWorld</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="https://eapj.org/on-slippery-ice/" class="">On Slippery Ice</a> at EAPJ</div></div>
</div>
<br class=""></div></body></html>