On 10.07.2016 17:44, Leon Kyneur wrote:
> Recently updated to 2.2.25. Noticed a migration script I've been
> previously running fine started giving me the errors below.
>
> Remove server doesn't log any failure. doveconf -n attached.
>
> + /bin/doveadm -o mail_fsync=never backup -R -u u...@domain
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 L
Recently updated to 2.2.25. Noticed a migration script I've been
previously running fine started giving me the errors below.
Remove server doesn't log any failure. doveconf -n attached.
+ /bin/doveadm -o mail_fsync=never backup -R -u u...@domain.com imapc:
dsync(u...@domain.com): Panic: file md
You sure you're not returning multiple password attributes from LDAP?
Aki
pass_attrs = 'mail=user, userPlaintextPassword=password_noscheme,
=proxy=y, =pass=%{ldap:userPlaintextPassword}, =host=%{ldap:mailstoreHost}'
I am returning the same password attribute into different fields :
pass
You sure you're not returning multiple password attributes from LDAP?
Aki
> On July 10, 2016 at 1:32 PM Leon Kyneur wrote:
>
>
> This turned into quite a large problem for me but think I have resolved it.
>
> After toying this a few settings I ended up (out of sheer desperation)
> setting "bl
This turned into quite a large problem for me but think I have resolved it.
After toying this a few settings I ended up (out of sheer desperation)
setting "blocking = yes" in my LDAP configuration.
Is this a logical thing to do? I couldn't find much on it other than i'm
guessing queries are no