Re: logfile support for MacOS

2019-01-23 Thread Larry Stone
I noticed what appears to be a cosmetic problem: log entries from master are being time-stamped with the time they were last started or “postfix reload”-ed rather than the current time and log entries from qmgr are being time-stamped with the time of the first activity since the start or reload.

Re: Postfix logging without syslogd

2019-01-23 Thread Larry Stone
Oops. Inadvertently posted this reply in the wrong topic. Reposting it hear for proper threading. === I noticed what appears to be a cosmetic problem: log entries from master are being time-stamped with the time they were last started or “postfix reload”-ed rather than the current time

Re: logfile support for MacOS

2019-01-23 Thread Larry Stone
Disregard. Reposted in the proper topic. -- Larry Stone lston...@stonejongleux.com > On Jan 23, 2019, at 10:35 AM, Larry Stone wrote: > > I noticed what appears to be a cosmetic problem: log entries from master are > being time-stamped with the time they were last started or “postfix > relo

Re: logfile support for MacOS

2019-01-23 Thread Wietse Venema
Larry Stone: > I noticed what appears to be a cosmetic problem: log entries from master are > being time-stamped with the time they were last started or ?postfix > reload?-ed rather than the current time and log entries from qmgr are being > time-stamped with the time of the first activity since

Re: logfile support for MacOS

2019-01-23 Thread Wietse Venema
Wietse Venema: > Larry Stone: > > I noticed what appears to be a cosmetic problem: log entries from master > > are being time-stamped with the time they were last started or ?postfix > > reload?-ed rather than the current time and log entries from qmgr are being > > time-stamped with the time of

Re: logfile support for MacOS

2019-01-23 Thread Wietse Venema
Larry, can you insert one line in src/util/msg_logger.c, or apply the patch at the end of this message? Wietse lt = localtime(&now) +VSTRING_RESET(msg_logger_buf); if ((len = strftime(vstring_end(msg_logger_buf), \ vstring_avail(msg_logger_buf), ***

flat down postfix to simple local sendmail forwarder

2019-01-23 Thread Matt Wong
Ok, so the title isn't really helpful, so I try to explain it: I want to use Apache James as my primary MTA (please don't ask why - just take it as given). Major issue: james doesn't have a local sendmail command replacement. So I've looked up apache james doc wich is heavy outdated. Also, I'm

Re: flat down postfix to simple local sendmail forwarder

2019-01-23 Thread Noel Jones
On 1/23/2019 1:47 PM, Matt Wong wrote: > Ok, so the title isn't really helpful, so I try to explain it: > > I want to use Apache James as my primary MTA (please don't ask why - > just take it as given). Major issue: james doesn't have a local > sendmail command replacement. So I've looked up apach

Re: logfile support for MacOS

2019-01-23 Thread Larry Stone
> On Jan 23, 2019, at 1:29 PM, Wietse Venema wrote: > > Larry, can you insert one line in src/util/msg_logger.c, > or apply the patch at the end of this message? Wietse, thanks - that did it! I’m seeing the timestamps I expect. With reference to the earlier notes, I do not have the expertise

Re: logfile support for MacOS

2019-01-23 Thread Wietse Venema
Larry Stone: > > > > On Jan 23, 2019, at 1:29 PM, Wietse Venema wrote: > > > > Larry, can you insert one line in src/util/msg_logger.c, > > or apply the patch at the end of this message? > > Wietse, thanks - that did it! I?m seeing the timestamps I expect. > With reference to the earlier notes

Re: Postfix logging without syslogd

2019-01-23 Thread Wietse Venema
Wietse Venema: > postfix-3.4-20190123-nonprod-logger has lightly-tested code for > logging to file without using syslogd. > > This solves a usability problem in MacOS, may help to work around > a logging bottleneck with systemd, and solves 99% of the problem > for logg