Hello all,

I have a 2 node director setup that uses checkpassword for authentication as well as backend assignment through director tags.

director_servers                = 192.168.1.10 192.168.1.20 director_mail_servers        = 192.168.2.10@srv1 192.168.2.11@srv2

checkpassword writes the following to Dovecot on successful authentication:

proxy=y\tdirector_tag=<tag>\tport=<port>ssl=yes\tdestuser=<email>\t

This seems to work just fine. However, when I attempt to view a users current hash/initial config:

# doveadm director status "user@domain.com" Current: n/a (expires -1) Hashed: Initial config:

I get null data. There does appear to be a hash mapping of some sort however:

# doveadm director map -u user@domain.com 1140334690

# doveadm director map -h 1140334690 user@domain.com

The use of doveadm director move has no effect. doveadm reports it moved the user, but it does not:

# doveadm -v director move "user@domain.com" 192.168.2.11 Info: User hash 1140334690 moved to 192.168.2.11

When using checkpassword and supplying fields to Dovecot, should I also be including another field to populate hashes for director? I could be missing something obvious in the docs.

I'm on version 2.3.18 (9dd8408c18). I have not included dovecot.conf due to the size. If someone needs to see it I can supply it.