search for: noreplicate

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 nor...

...e database. >>>> >>>> For the non-overlapping accounts in both servers I want to prevent >>>> replication, as it will otherwise fail with "Error: sync: Unknown user >>>> in remote". >>>> >>>> I have added "userdb_noreplicate" (also tried "userdb_noreplicate=y") >>>> for those users, but I still see the above error message in the logs. >>>> >>>> Like: >>>> reinob at bbmk.org:{SHA512-CRYPT}$6$e10...4c::::::userdb_noreplicate=y >>>> >>>&gt...

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 >...

...>-- >> >> i.e. I use a passwd-like database. >> >> For the non-overlapping accounts in both servers I want to prevent >> replication, as it will otherwise fail with "Error: sync: Unknown user >> in remote". >> >> I have added "userdb_noreplicate" (also tried "userdb_noreplicate=y") >> for those users, but I still see the above error message in the logs. >> >> Like: >> reinob at bbmk.org:{SHA512-CRYPT}$6$e10...4c::::::userdb_noreplicate=y >> >> If I run "doveadm user -u reinob at bbmk....

...A512-CRYPT username_format=%Lu /etc/dovecot/virtual_passwd } -->>-- i.e. I use a passwd-like database. For the non-overlapping accounts in both servers I want to prevent replication, as it will otherwise fail with "Error: sync: Unknown user in remote". I have added "userdb_noreplicate" (also tried "userdb_noreplicate=y") for those users, but I still see the above error message in the logs. Like: reinob at bbmk.org:{SHA512-CRYPT}$6$e10...4c::::::userdb_noreplicate=y If I run "doveadm user -u reinob at bbmk.org" I get the following: userdb: reinob at b...

I've set up replication as per the wiki under 2.3.3 and in my SQL user query I am returning a 'noreplicate' field, this is a boolean and returns true for all users at the moment. However when I do "doveadm replicator status '*'" it lists all users in my database suggesting it is trying to sync all users regardless of the noreplicate field. ``` user_query = SELECT home, uid, gid...

....e. I use a passwd-like database. >>> >>> For the non-overlapping accounts in both servers I want to prevent >>> replication, as it will otherwise fail with "Error: sync: Unknown user >>> in remote". >>> >>> I have added "userdb_noreplicate" (also tried "userdb_noreplicate=y") >>> for those users, but I still see the above error message in the logs. >>> >>> Like: >>> reinob at bbmk.org:{SHA512-CRYPT}$6$e10...4c::::::userdb_noreplicate=y >>> >>> If I run "dovea...

...irtual_passwd > } > -->>-- > > i.e. I use a passwd-like database. > > For the non-overlapping accounts in both servers I want to prevent > replication, as it will otherwise fail with "Error: sync: Unknown user > in remote". > > I have added "userdb_noreplicate" (also tried "userdb_noreplicate=y") > for those users, but I still see the above error message in the logs. > > Like: > reinob at bbmk.org:{SHA512-CRYPT}$6$e10...4c::::::userdb_noreplicate=y > > If I run "doveadm user -u reinob at bbmk.org" I get the foll...

Hello! I finally took the time and spent two days to set up replication for my server and now I have a question or two. I initially set noreplicate userdb field to 1 for all but a test user, but I could still see in the logs that all mailboxes were trying to connect to the other server via SSH. Is that normal? Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: Remote command returned error 84: ssh -i /home/vmail/.ss...

On 22.6.2019 22.00, Reio Remma via dovecot wrote: > Hello! > > I finally took the time and spent two days to set up replication for > my server and now I have a question or two. > > I initially set noreplicate userdb field to 1 for all but a test user, > but I could still see in the logs that all mailboxes were trying to > connect to the other server via SSH. Is that normal? > > Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: > Remote command returned error 84: s...

On Mon, 17 Feb 2020, Aki Tuomi wrote: > I wonder if we are doing the noreplicate too late. Can you try adding > one of the non-overlapping users to the other site with noreplicate=y > and see if helps? Well that did it indeed! :) I created the reinob at bbmk.org at the other server (just the line in the passwd file, without creating any directory or anything) and the l...

I believe the userdb_ prefix is used when you want to provide userdb fields in a passdb context, or in the actual passwd-file file contents (/etc/dovecot/users). In default_fields, you should use the non-prefixed name, i.e. "noreplicate=y" Use `doveadm user -u <username>` to see what userdb fields are returned for a specific user. - Eirik On 2/6/2020 11:36 PM, mail at backprod.de wrote: > Hi, > > I have set up the sync and it is working but I only would like to sync some users. Currently this does not seem...

....2 Relevant Settings: File users: mail at domain.de:{SHA}hash:::t: passdb { driver = passwd-file args = username_format=%u /etc/dovecot/users } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users default_fields = uid=2222 gid=2222 home=/var/vmail/%d/%n userdb_noreplicate=t } After restart of dovecot I allways get all users with sudo doveadm replicator status "*" usernamepriority fast sync full sync success sync failed abuse at domain.net none 00:01:58 03:52:23 - y admin at domein.net none 00:01:58 03:52:23 -...

> On 6 Aug 2019, at 23.52, Reio Remma via dovecot <dovecot at dovecot.org> wrote: > > service doveadm { > user = vmail > } > > This seems to have fixed it. Here's hoping for no unforeseen side-effects. :) > > I still need allow dovecot_t ssh_exec_t:file { execute execute_no_trans open read }; for selinux, but there are no more errors in maillog and it

On 24.06.2019 16:25, Reio Remma wrote: > On 24.06.2019 8:21, Aki Tuomi wrote: >> On 22.6.2019 22.00, Reio Remma via dovecot wrote: >>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l >>> vmail backup.host.ee doveadm dsync-server -D -uuser at host.ee >>>

On 06.08.2019 23:17, Reio Remma via dovecot wrote: > On 24.06.2019 16:25, Reio Remma wrote: >> On 24.06.2019 8:21, Aki Tuomi wrote: >>> On 22.6.2019 22.00, Reio Remma via dovecot wrote: >>>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >>>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l >>>>

On 24.06.2019 8:21, Aki Tuomi wrote: > On 22.6.2019 22.00, Reio Remma via dovecot wrote: >> Hello! >> >> I finally took the time and spent two days to set up replication for >> my server and now I have a question or two. >> >> I initially set noreplicate userdb field to 1 for all but a test user, >> but I could still see in the logs that all mailboxes were trying to >> connect to the other server via SSH. Is that normal? >> >> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: >> Remote command...

Thank you for the reply. I have done the sync manually with "doveadm sync" command. But, I have not configured the replication yet. I am looking at the below webpage for the replication. https://wiki.dovecot.org/Replication I am using the dovecot version "2.2.36". I am confused with what needs to be done after reading that page. 1. They are talking about v2.3.1 and v2.2+.

...ld you please give me more details on this? Providing some sample settings will be more helpful for me, please. I don't understand your confusion. You are using 2.2.36, which is v2.2+ (meaning a version greater than 2.2). The documentation states you need at least 2.3.1 if you want to use the noreplicate feature. So you can't use that with 2.2.36, but as your goal is to replicate everything you don't need "noreplicate". Besides that I can't see any difference in configuring replication for 2.2/2.3. If you want to replicate emails with ssh you just have to follow the first sec...

Still not quite right for me. Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout during state=sync_mails (send=mails recv=recv_last_common) I'm not sure if there is an underlying replication error