On Tue, May 6, 2025 at 1:26 PM Timo Sirainen <t...@sirainen.com> wrote:
     On 6. May 2025, at 12.13, Odhiambo Washington via dovecot
     <dovecot@dovecot.org> wrote:
     >
     > Then I created my auth-sql.conf.ext shown above.
     > What I realized then is that the dovecot/auth service doesn't seem
     to be
     > running. Not sure why.

     It's only started when the first auth lookup is done. You could test
     also with "doveadm auth lookup" command what happens, and it should
     start the auth process then also.

     > May 06 12:02:20 pop3-login: Info: Login aborted: Logged out (auth
     service
     > reported temporary failure

     This again seems like there should be an error logged.

     > `doveadm log errors` gives no output.

     Well, that's weird..

     > Looking at https://doc.dovecot.org/2.4.1/core/admin/running.html,
     and comparing
     > with a system where I have installed Dovecot 2.4.1:
     >
     > root@mail:/etc/dovecot/conf.d# ps auxw|grep "dovecot"
     > root        9739  0.0  0.0   8872  4816 ?        Ss   14:47   0:00
     /usr/sbin/
     > dovecot -F
     > root        9741  0.0  0.0   5324  3280 ?        S    14:47   0:00
     dovecot/
     > anvil
     > root        9742  0.0  0.0   5428  3256 ?        S    14:47   0:00
     dovecot/log
     > root        9743  0.0  0.1  51976 10248 ?        S    14:47   0:00
     dovecot/
     > config

     This is expected at startup.

     > On an system running 2.3.21, I get:
     ...

     That seems to be actually serving clients, so more processes have
     started up.

     > Is it normal that the dovecot/auth is not listed as a running
     service for
     > 2.4.1?

     Yes, and it's the same for 2.3 when starting up (unless you have
     changed process_min_avail settings).

     > info_log_path = /var/log/dovecot.log

     Set also log_path = /var/log/dovecot.log - any errors logged there
     then?

Hi Timo,

I ultimately did pick up a dovecot.conf (for 2.4.x) that was shared on this ML
by @Joan_Moreau and customized the few obvious values to match my install.
That helped so much to get Dovecot behaving sanely.
I was able to run  `doveadm log errors`, which helped me figure out that what I
needed for default_password_scheme was SHA512-CRYPT instead of just SHA512.

Why the default install of Dovecot on my system doesn't do this still is a
mystery to me.
A512-CRYPT512-CRYPT
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
 In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions: http://www.catb.org/~esr/faqs/smart-
questions.html]
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to