Quite right. My mistake. The root cause in this case was musl libc in the
Alpine Linux 3.9 container image, whose syslog call uses dgram only, unlike
glibc, which will attempt stream as well. Thanks for pointing me in the
right direction.
FWIW, the new CHUNKING support (BDAT command) in Postfix
> On Feb 15, 2019, at 7:02 AM, Andrey Repin wrote:
>
>> The 3.4.0-RC2 version of Postfix appears to have dropped support for
>> logging via TCP Unix sockets.
>> As recently as 3.3.0 Postfix used a TCP Unix socket to connect to syslog.
>
> No. It used a UNIX domain socket, not TCP.
The OP mean
Lex Scarisbrick:
> The 3.4.0-RC2 version of Postfix appears to have dropped support for
> logging via TCP Unix sockets. As recently as 3.3.0 Postfix used a TCP Unix
> socket to connect to syslog. This is obliquely referenced in the release
> notes:
Postfix calls the syslog(3) system library func
Greetings, Lex Scarisbrick!
> The 3.4.0-RC2 version of Postfix appears to have dropped support for
> logging via TCP Unix sockets.
> As recently as 3.3.0 Postfix used a TCP Unix socket to connect to syslog.
No. It used a UNIX domain socket, not TCP.
> This is obliquely referenced in the releas
> On Feb 14, 2019, at 8:39 PM, Lex Scarisbrick wrote:
>
> The 3.4.0-RC2 version of Postfix appears to have dropped support for logging
> via TCP Unix sockets. As recently as 3.3.0 Postfix used a TCP Unix socket to
> connect to syslog. This is obliquely referenced in the release notes:
I'm af
The 3.4.0-RC2 version of Postfix appears to have dropped support for
logging via TCP Unix sockets. As recently as 3.3.0 Postfix used a TCP Unix
socket to connect to syslog. This is obliquely referenced in the release
notes:
[Incompat 20190126] This introduces a new master.cf service 'postlog'
wi
