search for: c1c67bdc8752

...Teemu Huovila wrote: >> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? > You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. > http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 > > br, > Teemu Huovila One last question. Is it possible to achieve this with system users and PAM or do I need to basically create a new static userdb for system users? Could this be done via a per-user LDA setting or sieve? Thanks, Reuben

...t;>>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >>> You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. >>> http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 >>> >>> br, >>> Teemu Huovila >> >> One last question. Is it possible to achieve this with system users and PAM or do I need to basically create a new static userdb for system users? > > You can create a new userdb passwd-file that adds extra fields. So...

Hi all, I've had an interesting use case come up which - to cut the story short - one way to solve the problem I am looking at may be to replicate a small number of mailboxes to a third remote server. I've currently had replication running between my main dovecot machine and another remote VM for some time and working well (so I'm not new to replication and I've got a good

...rs aside >>>>>> from a crude hack around system first and last UIDs? >>>>> You can set the userdb to return an empty mail_replica >>>>> variable for users you want to exclude from replication. >>>>> http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 >>>>> >>>>> br, Teemu Huovila >>>> >>>> One last question. Is it possible to achieve this with system >>>> users and PAM or do I need to basically create a new static >>>> userdb for system users? >>> >>&g...

.../MainIndex?highlight=%28endian%29 > Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 br, Teemu Huovila

...la wrote: >>> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >> You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. >> http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 >> >> br, >> Teemu Huovila > > One last question. Is it possible to achieve this with system users and PAM or do I need to basically create a new static userdb for system users? You can create a new userdb passwd-file that adds extra fields. So something like: userdb {...

...t;> Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? >>>> You can set the userdb to return an empty mail_replica variable for users you want to exclude from replication. >>>> http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 >>>> >>>> br, >>>> Teemu Huovila >>> >>> One last question. Is it possible to achieve this with system users and PAM or do I need to basically create a new static >>> userdb for system users? >> >> You can create a new user...

Hi People, I recently setup a replication service within dovecot between two machines in different datacenters, which has the following configuration; (yes it is hashed out, because I needed to) #service replicator { # unix_listener replicator-doveadm { # mode = 0666 # } # process_min_avail = 1 #} # #service aggregator { # fifo_listener replication-notify-fifo { # mode = 0666 #