Bug: 'noreplicate' database extra field ingnored

Phil
Mon, 22 Oct 2018 18:24:07 -0000

On 22 Oct 2018, at 8:08, Aki Tuomi wrote:

> On 20.10.2018 7.29, Phil wrote:
>> The 'noreplicate' user database field described in the wiki
appears
>> to
>> make no difference as to whether an account gets replicated or not.
>> My sql user query returns a 'noreplicate' field and I can
confirm
>> that
>> this is getting set using 'doveadm user', however when I add a
new
>> account with noreplicate=true it gets replicated regardless.
>>
>> User query:
>> user_query = SELECT home, uid, gid, noreplicate FROM mail_accounts
>> WHERE address = '%u'
>>
>> # doveadm user user1 at mydomain.com
>> field??? value
>> uid??? 1000
>> gid??? 1000
>> home??? /mail/domains/mydomain.com/user1/Maildir
>> mail??? maildir:/mail/domains/mydomain.com/user1/Maildir
>> noreplicate??? t
>>
>>
> Can you turn on 'mail_debug=yes' and provide logs for a noreplicate
> user
> being replicated?
>
> Aki


I added a new user 'reptest' with noreplicate='t' and have
attached the
logs from both ends of the replication pair.
You can see that the account was replicated and I have verified this by
sending an email to the account and it immediately appears on both
servers.
-Phil
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mail1_debug.log
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20181022/ebe5cc46/attachment-0002.log>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mail2_debug.log
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20181022/ebe5cc46/attachment-0003.log>