dsync selectively

[lejeczek]

On 18/06/15 14:01, Teemu Huovila wrote:
> On 06/17/2015 06:07 PM, lejeczek wrote:
>> On 16/06/15 14:27, lejeczek wrote:
>>> On 16/06/15 14:16, lejeczek wrote:
>>>> On 16/06/15 13:14, B wrote:
>>>>> P,
>>>>>
>>>>> On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote:
>>>>>
>>>>>> I've barely started reading on dsync and I wonder..
>>>>>> would you know if it is possible to sync/replicate only specific
>>>>>> domain(users)? or it's always the whole lot?
>>>>> See
>>>>> http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html
>>>>>
>>>>> basically set 'mail_replica' to 'remote:server3' in your userdb
>>>>>
>>>>>
>>>>> B
>>>>>
>>>> thanks B,
>>>> userdb as appose to plugin?
>>>> it's quite unclear what to put there, to a beginner.
>>>>
>>> also if I put mail_replica (having the rest, pretty much take form wiki in repl.conf) into userdb
>>> I get:
>>>
>>> line 24: Unknown setting: mail_replica
>>>
>>> this userdb uses ldap driver in case it may matter, I guess it should not.
>>>
>> gee, I cannot figure it out, and I'd guess it must be sort of typical situation,
>> where one would want to avoid replication os local/system users and only sync a virtual domain(s), no?
>> Can it be done by means of config files?
> What the original answer meant was, that you should put it in your userdb backend, in this case LDAP. So add a field in LDAP,
> which for users you want to replicate points to the replication destination and for other users is blank. then add it via a LDAP
> attribute template, e.g.
>
> user_attrs = \
>     =mail_replica=%{ldap:nameOfFieldContainingReplica}
>
> Make sure (with auth_debug=yes and mail_debug=yes in your config)the mail_replica is empty for users you do not want to replicate.
>
> Please read http://wiki2.dovecot.org/AuthDatabase/LDAP/Userdb http://wiki2.dovecot.org/Replication?highlight=%28mail_replica%29
> and http://wiki2.dovecot.org/Tools/Doveadm/Sync?highlight=%28mail_replica%29 carefully.
>
> br,
> Teemu Huovila
>
ok, I hope I'm beginning to understand this,
do we have an attribute good for this? Common/default 
schemas do not seem to provide anything suitable.
many thanks.