Use of pkg-config to detect libicu

2019-02-16 Thread Scott Kitterman
Apparently the libicu upstream has deprecated use of icu-config and recommends pkg-config instead. Debian has recently decided to stop shipping icu-config for obscure distro related reasons. The Debian libicu maintainer suggests this as an alternative (and it works here): --- postfix-3.3.2.or

Re: Use of pkg-config to detect libicu

2019-02-16 Thread Wietse Venema
Scott Kitterman: > Apparently the libicu upstream has deprecated use of icu-config and recommends > pkg-config instead. Debian has recently decided to stop shipping icu-config > for obscure distro related reasons. The Debian libicu maintainer suggests > this as an alternative (and it works here

Re: 3.3.0 -> 3.3.2 and sasl error

2019-02-16 Thread sashk
Hello Patrick, Thanks for the response. > The other side offers PLAIN LOGIN, but your smtp client doesn't like that > because those are mechanisms which send identification data in clear (read: > unencrypted). That's because you have this (default) in place: > > smtp_sasl_security_options = no

Re: 3.3.0 -> 3.3.2 and sasl error

2019-02-16 Thread sashk
Turns out this wasn't something wrong with the postfix. But in case someone will run into the same issue -- here is how I addressed this problem: Alpine 3.9 splitted package libsasl (which used to contain liblogin and libplain[1]) into three: libsasl[2], cyrus-sasl-plain[3] and cyrus-sasl-login

Re: 3.3.0 -> 3.3.2 and sasl error

2019-02-16 Thread Andrey Repin
Greetings, sashk! > Hello Patrick, > Thanks for the response. >> The other side offers PLAIN LOGIN, but your smtp client doesn't like that >> because those are mechanisms which send identification data in clear (read: >> unencrypted). That's because you have this (default) in place: >> >> smtp

Re: 3.3.0 -> 3.3.2 and sasl error

2019-02-16 Thread Bill Cole
On 16 Feb 2019, at 15:46, Andrey Repin wrote: Greetings, sashk! Hello Patrick, Thanks for the response. The other side offers PLAIN LOGIN, but your smtp client doesn't like that because those are mechanisms which send identification data in clear (read: unencrypted). That's because yo

Re: 3.3.0 -> 3.3.2 and sasl error

2019-02-16 Thread Viktor Dukhovni
On Sat, Feb 16, 2019 at 11:46:12PM +0300, Andrey Repin wrote: > > submission inet n - n - - smtpd > > -o syslog_name=postfix/submission > > -o smtpd_tls_security_level=encrypt > > This is NOT right. > submission (port 587/tcp) is a plan connection. Unencrypted. >