I am also seeing this error since updating to 2.2.25. I do believe it's
only occurring on CRAM-MD5, DIGEST-MD5 and NLTM auth.
# dovecot --version
2.2.25 (7be1766)
Jul 26 02:10:57 auth-worker(11499): Info:
ldap(username,192.168.10.9,): unknown user - trying
the next passdb
Jul 26 02:10:57
I was more thinking about login methods, such as NTLM or CRAM-MD5. Or
whether the user is present or missing. Or combination of these.
Aki
On 13.07.2016 08:04, Alexey Asemov (Alex/AT) wrote:
> Checked logs, it looks like completely random to me.
>
> We do have users with special chars in
Checked logs, it looks like completely random to me.
We do have users with special chars in passwords, including + - { } and
so on, but log content on crashes don't seem related at all.
KR,
Alex
On 12.07.2016 16:34, Aki Tuomi wrote:
On 11.07.2016 20:58, Alexey Asemov (Alex/AT) wrote:
On 11.07.2016 20:58, Alexey Asemov (Alex/AT) wrote:
Hello Aki.
Did you by chance test if this happens always, or in particular conditions?
Aki
Hello Aki.
Here it is. Some sensitive data was replaced by ***.
# 2.2.25 (7be1766): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.15 (97b3da0)
# OS: Linux 3.10.0-***.el7.x86_64 x86_64 CentOS Linux release 7.***
(Core) ext4
auth_cache_negative_ttl = 15 secs
auth_cache_size = 8 M
On 09.07.2016 10:55, Alexey Asemov (Alex/AT) wrote:
> 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(u...@domain.org,*.*.*.*,): unknown user
> Jul 9 00:00:14
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(u...@domain.org,*.*.*.*,): unknown user
Jul 9 00:00:14 LXmail01 dovecot: auth: Panic: file auth-request.c: line
1049
