search for: replication_sync_timeout

DOVECOT -N # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 2.6.32-431.23.3.el6.x86_64 x86_64 CentOS release 6.9 (Final) '''' plugin { ''' mail_replica = tcp:10.1.1.20:1111 # replication_sync_timeout = 2s replication_sync_timeout = 2 '''' } '''' ? /VAR/LOG/DOVECOT/DOVECOT.LOG doveadm(lty at cndns.com): Error: replication(lty at cndns.com): Invalid replication_sync_timeout value: 2s I am talking about the replication_sync_timeout = 2s in the config...

DOVECOT -N # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 2.6.32-431.23.3.el6.x86_64 x86_64 CentOS release 6.9 (Final) '''' plugin { ''' mail_replica = tcp:10.1.1.20:1111 # replication_sync_timeout = 2s replication_sync_timeout = 2 '''' } '''' /VAR/LOG/DOVECOT/DOVECOT.LOG doveadm(lty at cndns.com): Error: replication(lty at cndns.com): Invalid replication_sync_timeout value: 2s I am talking about the replication_sync_timeout = 2s in the configurat...

...e a "service auth" enabled though... it's used for Postfix SASL? > to authenticate SMTP. > > > I'm running > > > # dovecot --version > 2.2.24 (a82c823) > > > > > > Cheers, > Jean-Luc > > > > > > PS: "replication_sync_timeout = 2s" doesn't work, I had to drop the 's' > > > > > > On 2016-08-28 17:43, Jean-Luc Wasmer wrote: >> >> >> Hi, >> >> >> >> >> >> I?m having a hard time with the?http://wiki2.dovecot.org/Replication...

Sorry for the re-post - just want to make sure you saw this: #0 0x00007fddaf597c37 in __GI_raise (sig=sig at entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fddaf59b028 in __GI_abort () at abort.c:89 #2 0x00007fddaf9c0c86 in default_fatal_finish (type=<optimized out>, status=status at entry=0) at failures.c:201 #3 0x00007fddaf9c0d6e in i_internal_fatal_handler

Hi, I?m having a hard time with the?http://wiki2.dovecot.org/Replication ?page. - for a master-master setup, does the configuration need to be mirrored on both masters? - after aggregating unrelated sections of the wiki page, there seems to be 3 different values for ?mail_replica": - "remote?: for SSH - ?remoteprefix": for SSH wrapper - ?tcp?: for?TCP connection using

On 24 Mar 2017, at 3.46, Daniel Miller <dmiller at amfes.com> wrote: > > #14 replicator_queue_handle_sync_lookups (user=0xfa3fc0, queue=0xf92260) at replicator-queue.c:278 Oh, you're using synchronous replication (replication_sync_timeout setting). I don't think it's been tested much.

...ator { unix_listener replicator-doveadm { mode = 0600 } } replication_max_conns = 10 plugin { # When saving a new mail via IMAP or delivering a mail via LDA/LMTP, # wait for the mail to be synced to the remote site. If it doesn't finish # in 2 seconds, return success anyway. # replication_sync_timeout = 2s } ??? Is the Dsync setting bad? please tell me. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200223/ca356835/attachment.html>

...} mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:imap2:9943 replication_sync_timeout = 2 } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service config { unix_listener config { user = dovecot } } service doveadm {...

...ice replicator { unix_listener replicator-doveadm { mode = 0600 }} replication_max_conns = 10 plugin { # When saving a new mail via IMAP or delivering a mail via LDA/LMTP, # wait for the mail to be synced to the remote site. If it doesn't finish # in 2 seconds, return success anyway. # replication_sync_timeout = 2s}---* But replication gives an error --- *Error: open(/var/run/dovecot/replication-notify-fifo) failed: Permission denied* --- Why is this? By the way, When 30-dsync.conf is changed as follows, it works only for one user *---service aggregator { fifo_listener replication-notify-fif...

...sieve_extensions = +duplicate +notify +imapflags +vacation-seconds > sieve_global_dir = /usr/local/etc/dovecot/sieve > sieve_before = /usr/local/etc/dovecot/sieve/duplicates.sieve > > > mail_replica = tcp:10.221.0.19:12345 > #mail_replica = remote:vmail at 10.221.0.19 > #replication_sync_timeout = 2 > > fts = lucene > fts_lucene = whitespace_chars=@. > fts_autoindex = yes > fts_languages = en > } > > #sieve_extensions = vnd.dovecot.duplicate > > #sieve_plugins = vnd.dovecot.duplicate > > service anvil { > process_limit = 1 > c...

...onds >> ?sieve_global_dir = /usr/local/etc/dovecot/sieve >> ?sieve_before = /usr/local/etc/dovecot/sieve/duplicates.sieve >> >> >> ?mail_replica = tcp:10.221.0.19:12345 >> ?#mail_replica = remote:vmail at 10.221.0.19 <mailto:vmail at 10.221.0.19> >> ?#replication_sync_timeout = 2 >> >> ?fts = lucene >> ?fts_lucene = whitespace_chars=@. >> ???????fts_autoindex = yes >> ???????fts_languages = en >> } >> >> #sieve_extensions = vnd.dovecot.duplicate >> >> #sieve_plugins = vnd.dovecot.duplicate >> >> ser...

One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jan 06 00:50:32 replicator: Fatal: master:

...either high (new mails) or low (everything else). Optionally the replication plugin can also support synchronous replication of new mail deliveries. In this way it connects to replication-notify UNIX socket, tells it to replicate the user with sync (=highest) priority and waits until it is done or replication_sync_timeout occurs. The IMAP/LMTP client won't see an "OK" reply until the mail is replicated (or the replication has failed). The synchronous replication probably adds a noticeable delay, so it might not be acceptable for IMAP, but might be for LMTP. So, what is listening in those replication-n...

So nobody has any idea why this could happen? Let me know if I should provide more Information Thanks Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis at gdv-dl.de<mailto:Thomas.Tsiakalakis at gdv-dl.de> GDV Dienstleistungs-GmbH Glockengie?erwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de>