search for: director_tag

Hello all, I'm working with director in tandem with 'director_tags' to group some backend hosts. I've assigned the groups to the hosts by appending a '@' character after the IP address of a backend host under director_mail_servers: ... director_mail_servers = 192.168.0.1 at foo 192.168.0.2 at bar 192.168.0.3 at foobar ... I can confirm that...

...the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated user-addresses are included via a passwd-file with entries like: grtest1 at hrz.uni-marburg.de:::::::director_tag=hrz protocol=smtp user=grtest1 grtest2 at hrz.uni-marburg.de:::::::director_tag=hrz protocol=smtp user=grtest2 ... The director_tag points to the old mailbox-server, with 'protocol=smtp' SMTP is used for delivery, as the old machine is not capable of LMTP. The setup works fine for imap-pr...

Hey, Does anyone know how the new(ish) director tags work in respect to which one is select for a user ?? Is there a query or field returned on userdb lookup to specify the director tag to use ??? rgds Matt

...e other nodes. Director should be able to send the connection to a node that has the same data as it's neighbors, Allowing high availability. What I've experimented with so far: _Server pairs, using dsync to replicate data between the nodes - Director to send users to a specific pair (director_tag returned from passdb) _ ??? Pros: ??? - Easy way to replicate data, without the need for external tools ??? Cons: ??? - Limited to one pair of nodes ??? - dsync doesn't replicate all sieve files, for example, one file that tracks out of office replies has not been replicated in my e...