Hi
Sorted....
After reading changelog of latest sources and noting comments about corrected problems with inet_listener <name> I made the following change which resolved the short response from the sasl inet socket as seen with telnet
inet_listener auth-userdb { address = 192.168.3.112 port = 12345 ssl = yes }
to inet_listener { address = 192.168.3.112 port = 12345 ssl = yes } or
inet_listener auth-inet { address = 192.168.3.112 port = 12345 ssl = yes }
seems auth-userdb as a name screws something.
auth sasl over inet socket no working 100% ok
Paul
On 15/06/2016 09:04, aki.tuomi@dovecot.fi wrote:
On June 15, 2016 at 1:50 AM Paul <paul@enlund.co.uk> wrote:
Hi This is my 1st time here so please be gentle.
I have encountered one problem since upgrading from 2.0.19 to 2.2.9 which has me beat. The system provides sasl auth services via inet to a postfix 2.11 system. Since the upgrade postfix complains of no sasl methods available. The same dovecot configuration is used on both versions. Now I get these results looking at the inet connection
Version 2.0.19 root@larch:~# telnet 192.168.3.15 12345 Trying 192.168.3.15... Connected to 192.168.3.15. Escape character is '^]'. VERSION 1 1 MECH PLAIN plaintext MECH LOGIN plaintext MECH CRAM-MD5 dictionary active SPID 23223 CUID 1 COOKIE d0b71942d48585303f9ae4681baabf87 DONE
Version 2.2.9 root@larch:~# telnet 192.168.3.112 12345 Trying 192.168.3.112... Connected to 192.168.3.112. Escape character is '^]'. VERSION 1 1 SPID 5300
Seems be something lacking in the response from 2.2.9 that fits the "no sasl methods" response from postfix
have you checked
doveadm log errors
Aki Tuomi