So, going to latest 2.2 RPM from ATRPMs does seem to fix the problem
(that is, the same config works as expected).
So, my question then is, in terms of indices, dovecot-uidlist, etc., is
it safe to move from Dovecot 1.0.7 directly to 2.2.10?
Also, even if I put:
doveadm_socket_path = localhost:88
I'm guessing this is the most significant issue:
Jun 3 16:22:33 retr01 dovecot: director: Fatal: No inet_listeners defined for
director service (for standalone keep director_servers empty)
What confuses me, is that not only do I have this in my config:
service director {
fifo_listener login/
And I realize that doveadm isn't setup properly yet, and that
director_doveadm_port needs to be doveadm's inet_listener, not
director's as it is now. Presumably this should just affect being able
to run doveadm, though, and not cause the problems I mentioned?
It would be really convenient if runni
I'm experiencing some problems similar to those described in
http://dovecot.org/list/dovecot/2012-July/137250.html
except with 2.0.9.
Adding http://dovecot.org/list/dovecot/2012-July/084906.html
to the main config didn't seem to help, nor did setting the list of
director and backend servers to ju
