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
> 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
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()
+VSTRING_RESET(msg_logger_buf);
if ((len = strftime(vstring_end(msg_logger_buf), \
vstring_avail(msg_logger_buf),
***
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
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
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
>
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
> "Wietse" == Wietse Venema writes:
Wietse> John Stoffel:
>> > "Wietse" == Wietse Venema writes:
>>
Wietse> I'm implementing logfile support for Postfix on MacOS, because not
Wietse> providing results in a bad experience.
>>
Wietse> This is a retrofit workaround, therefore it will
John Stoffel:
> > "Wietse" == Wietse Venema writes:
>
> Wietse> I'm implementing logfile support for Postfix on MacOS, because not
> Wietse> providing results in a bad experience.
>
> Wietse> This is a retrofit workaround, therefore it will have limitations
> Wietse> that do not exist with
On Fri, January 18, 2019 9:24 pm, John Stoffel wrote:
>> "Wietse" == Wietse Venema writes:
>
> Wietse> I'm implementing logfile support for Postfix on MacOS, because not
> Wietse> providing results in a bad experience.
>
> Wietse> This is a retrofit workaround, therefore it will have
> "Wietse" == Wietse Venema writes:
Wietse> I'm implementing logfile support for Postfix on MacOS, because not
Wietse> providing results in a bad experience.
Wietse> This is a retrofit workaround, therefore it will have limitations
Wietse> that do not exist with the default syslog-based
On Jan 18, 2019, at 2:18 PM, Wietse Venema wrote:
> I'm implementing logfile support for Postfix on MacOS, because not
> providing results in a bad experience.
Wietse, I’m impressed. As I run Postfix on a couple of Macs in a non-critical
environment (outgoing only for messages from system
I'm implementing logfile support for Postfix on MacOS, because not
providing results in a bad experience.
This is a retrofit workaround, therefore it will have limitations
that do not exist with the default syslog-based implementation.
- The logfile pathname is configured in main.cf, and
13 matches
Mail list logo
