Since it was a container, I was not running any syslog, just using the log modules from docker. This is a sample output from postfix stdout. I fixed it using syslog-ng within the container.
Em sáb., 6 de nov. de 2021 às 09:56, Curtis Maurand <cur...@maurand.com> escreveu: > On Fri, 2021-11-05 at 13:34 -0300, Rafael Azevedo wrote: > > One last thing, is it possible to change the date format of the output? > > Current format: > Nov 05 13:20:06 smtp21 postfix/smtp[136]: 9D86C60BBE > > I'd like to use ISO format: > 2021-10-29T19:37:52.017684-03:00 smtp21 postfix/smtp > > Could that be possible? > > > > My systems use rsyslog. The timestamp format is configurable. > > > Thanks > > Em sex., 5 de nov. de 2021 às 13:10, Rafael Azevedo <raf...@gmail.com> > escreveu: > > Thanks Wietse, > > After disabling chroot, everything worked just as expected. > > Thanks a lot guys. > > BR, > R > > Em sex., 5 de nov. de 2021 às 13:01, Wietse Venema <wie...@porcupine.org> > escreveu: > > Rafael Azevedo: > > After disabling chroot, it worked! > > LINUX bites, if chroot breaks relative pathnames for UNIX-domain > DGRAM sockets. > > (If chroot broke relative pathnames for UNIX-domain STREAM sockets, > there should have been lots of bug reports already). > > > Any clue about how can I have milliseconds in this output? > > That is currently not implemented. > > Postfix alreadey provides sub-second logging for different stages > of delivery (time since arrival, time in active queue, time to > connect, time to transmit message). > > http://www.postfix.org/postconf.5.html#delay_logging_resolution_limit > > Example: > > Nov 5 11:48:59 spike postfix/local[445]: 4Hm4gH1RlnzJrP5: to=< > spam...@porcupine.org>, relay=local, delay=0.21, > delays=0.2/0.0003/0/0.0036, dsn=2.0.0, status=sent (delivered to command: > umask 077; exec /usr/local/bin/filter) > > Wietse > >
