I ran into this myself a little while back. Used Bill’s logging example until I ironed out a few glitches. Now everything is working ok I don’t use it.
I’m on a Mac by the way. OSX 10.14.2 and run an apache vhosts web setup, Postfix with Dovecot + MySQL, and Clamd, freshclam etc etc. Postfix and Dovecot compiled myself to get around Apple’s broken installs. I think everything else is either brew or macports, like Unbound, openssl, dmarcian and so on. It’s a 2TB SSD system now, with 16GB RAM, on a SKY Fibre MAX line. And yes, it’s dynamic DNS much to my disappointment and they won’t change it. And for some obscure reason SKY have listed the netblock in the spamhause rbl database. Which I have to keep unlisting it from. But for the radio stream I use NOIP.com, and for the mail server when/if the IP changes - and it’s noticable as soon as it does, I just go to the DNS config on my provider and reset it to the current. Fortunately it doesn’t change often because the server and router is never turned off. Rarely anyway. So I’m making do, and that’s hardly Apple’s fault. As a server it runs ok for my needs. But I don’t have an office full of users so can’t comment on it’s scalability. Dovecot logging works fine. Postfix if I use Bill Cole’s option. It’s also possible to fine tune that command line to get better granularity - see the man pages and the online wiki. > On 10 Jan 2019, at 15:54, Larry Stone <lston...@stonejongleux.com> wrote: > > > > > >> On Jan 9, 2019, at 9:48 PM, James Brown <jlbr...@bordo.com.au> wrote: >> >>> On 10 Jan 2019, at 2:01 pm, Larry Stone <lston...@stonejongleux.com> wrote: >>> >>> Is this a recent build of Dovecot or was it built on an older version of >>> MacOS before the logging changes? If the former, ask on the Dovecot list >>> how they did it. If the latter, it’s a meaningless data point until Dovecot >>> is rebuilt on a newer version of MacOS. >>> >> >> Hi Larry. It’s a recent build of Dovecot, compiled on Mojave. > ... >> >> The setting file for logging, “etc/dovecot/conf.d/10-logging.conf” does have >> this: >> >> ## >> ## Log destination. >> ## >> >> # Log file to use for error messages. "syslog" logs to syslog, >> # /dev/stderr logs to stderr. >> #log_path = syslog >> log_path = /var/log/mail.log >> >> So I’ve had to change this so that it writes directly to the file, and not >> to syslog. > > Ah. So Dovecot has the ability to write logs directly. I believe Wietse has > stated in the past that no such capability exists in Postfix and it only logs > to the syslog daemon. And it’s the changes Apple has made to syslog that are > the issue. > > Bill Cole posted (again) a workaround that you can pursue. Beyond that, > unless Wietse decides to modify Postfix’s logging to support alternate > methods such as Dovecot does (and I have not the slightest clue how involved > that might be - you’re welcome to do it yourself if you’re so inclined), we > really don’t have a solution given Apple’s decision to move away from the > Unix standard for logging. > > Bill also stated that MacOS is no longer a suitable platform for being a > server and I largely concur. I used to run a full mail server but gave up on > that three years ago and moved my mail to an outside service (and as I now > have a provider that blocks port 25, not an option for me anymore anyway). I > still run Postfix but only for getting system generated emails off the system > to my outside mail service (I have some system status processes that alert me > to various issues that can occur) so logging is not the concern for me today > that it was when I was running the full server. > > -- > Larry Stone > lston...@stonejongleux.com >
