Hello,
Since updating to 2.2.25, we do have the following issue (seems to be related to the new auth policy code):
Jul 9 00:00:14 LXmail01 dovecot: auth-worker(6558): sql(user@domain.org,*.*.*.*,<wjpa7SY3nNFR8yTo>): unknown user Jul 9 00:00:14 LXmail01 dovecot: auth: Panic: file auth-request.c: line 1049 (auth_request_lookup_credentials): assertion failed: (request->credentials_scheme == scheme) Jul 9 00:00:14 LXmail01 dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d57e) [0x7f197bd8157e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8d65e) [0x7f197bd8165e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f197bd201f6] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c44715a] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c453f8f] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c446d2b] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c4 46e28] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c457742] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c457f06] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c44d65a] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f197bd94edc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_in ternal+0xff) [0x7f197bd9633f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f197bd94f65] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f197bd95118] -> /usr /lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f197bd26663] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c43cbe1] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f197b30ab15] -> dovecot/auth 1 wait, 0 passdb, 0 userdb [0x7f197c43cdd1] Jul 9 00:00:14 LXmail01 dovecot: auth: Fatal: master: service(auth): child 6555 killed with signal 6 (core dumps disabled) Jul 9 00:00:14 LXmail01 dovecot: pop3-login: Warning: Auth connection closed with 1 pending requests (max 1 secs, pid=8133, EOF)
Environment is MySQL passdb/userdb, we are using plain scheme as default and password_noscheme field. In 2.2.24 and below auth worked without scratch. Reverting all policy-related commits in 2.2.25 fixes this, but I have not dug the details.
KR,
Alex