Hi all, I just wanted to say thanks for all your efforts and bringing this looking to be promising release together.
I spent the last two days tinkering with old and new configurations. Sadly I had to revert back to 2.3.21ðŸ˜. Everything worked just fine including compression and sieve and secure connections except Exim with Dovecot LMTP and authenticator. There seem to be a bug, only occurs when I attempt to send remote email, I connect to smtp via Exim which uses dovecot auth-client socket to authenticate user, dovecot accepts the connection from Exim, makes sql driver query from mysql to check passdb, and stalls there forever and noticed it keeps opening more and more and more connections with unique fd until it reaches anvil limit and disallow logins and if I disable anvil service like it was recommended in documentation, it reaches max user connected using same ip address limit and disallow logins again. I tinkered so much with permissions and both exim and dovecot logs trying to find any lead to fix yet to no avail I found way, as everything works fine when I return to 2.3.21. using old yet identical configuration. One thing I remember happened before and its similar in terms of exim authentication stalling experience, its when I set ssl = yes inside lmtp service in 2.3.21 and when I remove it works fine. Along this, I noticed the only different configuration its the address member in the lmtp service referenced here https://doc.dovecot.org/2.4.0/core/config/delivery/lmtp.html#lmtp-server When I set it, dovecot 2.4 fails to start service and returns " address " unrecognised option. Its quite strange and not sure why its still in documentation page which was updated few days ago, on the 27th. I had to remove it while in 2.3.21 I can set it to the smtp server address which exim makes lmtp call to byname and works fine. Dovecot 2.4 works fine with receiving remote emails since no authentication is required from mta agent, exim since it just transports the email to lmtp transport and forward it to dovecot. I hope the team to review this bug when they have the chance and address it in the incoming release. I am really excited to give dovecot 2.4 another try hopefully with much better release. In case I missed anything which with I can fix this problem, I would also appreciate if anyone let me know. With thanks. Zakaria. _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
