director / main instance

Will Yardley
Tue, 15 Jul 2014 03:48:04 -0000

I have directors and backend servers running on the same systems (x3).
To be able to run doveadm foo with a minimum of fuss (without having to
list socket paths explicitly), should it be the director that's the
"default"? If so, is it safe to symlink '/var/run/dovecot' to
'/var/run/dovecot-director', or should I just make the director's
base
path /var/run/dovecot directly?

in dovecot-director.conf, I have:

service doveadm {
  inet_listener {
    port = 8889
  }
}
local 192.168.x.0/24 {
  doveadm_password = Foo
}
doveadm_proxy_port = 8888

and in dovecot-main.conf, I have:

service doveadm {
  inet_listener {
    port = 8888
  }
}
local 192.168.x.0/24 {
  doveadm_password = Foo
}
protocol doveadm {
  auth_socket_path = director-userdb
}

Is this correct (and is there anything unneeded / redundant there)?


# dovecot instance list
path                               name     last used           running
/var/run/dovecot-director          director 2014-07-14 20:36:49 yes
/var/run/dovecot-main              main     2014-07-14 20:36:49 yes

# dovecot director status
mail server ip vhosts                           users
192.168.x.xx      100                               2
192.168.x.xx      100                               0
192.168.x.xx      100                               0