similar to: Dsync replication - delayed replication (Sync lock)

Displaying 20 results from an estimated 3000 matches similar to: "Dsync replication - delayed replication (Sync lock)"

2020 Aug 19
3
sieve_max_script_size is ignored
I am in troubles with compiling sieve scripts larger than 1MB. I see in logs following errors: Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: line 16818: quoted string started at line 3 is too long (longer than 1048576 bytes) Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>:
2020 Aug 19
1
sieve_max_script_size is ignored
That's what I was afraid of. Some users are trying to set up vacation message with inline picture. I am aware it's not ideal but in some cases it's needed. It would be nice if this configuration option works in the future. Regards, Zdenek On 8/19/20 5:01 PM, Stephan Bosch wrote: > > > Op 19-8-2020 om 13:47 schreef Zden?k Z?me?n?k: >> I am in troubles with compiling
2020 Aug 19
0
sieve_max_script_size is ignored
Op 19-8-2020 om 13:47 schreef Zden?k Z?me?n?k: > I am in troubles with compiling sieve scripts larger than 1MB. > I see in logs following errors: > Aug 19 13:10:26 mail dovecot: lmtp(z.z at xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: line 16818: quoted string started at line 3 is too long (longer than 1048576 bytes) > Aug 19 13:10:26 mail dovecot:
2019 Oct 09
1
Sieve replication - Debian 9.11 - Dovecot 2.2.7 - script changes not replicated
Hi, I am trying to setup Sieve replication, it is almost working: 1/ Create a script - sync'd across 2/ Activate/de-activate a script - change sync'd 3/ Delete a script - change sync'd But if I make a change to a script it is not replicated, unless I de-activate and activate again. I am seeing in the logs the below during this process (de-activating/activating): Oct? 9
2020 May 31
1
auth_policy_server vs client_id and x-originating-ip
I run into troubles when trying to set up auth_policy_server in Dovecot 2.3.10.1. It works almost as expected but I cannot get client ID in this process. By setting up "imap_id_log=*" I see in log that Dovecot gets details about mail client like name and version: May 31 14:20:58 mail dovecot: imap(xxx at example.xxx)<24796><ft7ytfCmjdZWMSZQ>: ID sent: name=Thunderbird,
2019 Sep 30
1
Sieve replication - does not replicate
Hi, I have two servers replicating mail as required, the directory structure (per user), however they will not replicate the sieve scripts directory: server 1 Maildir sieve server 2 Maildir Output of doveconf -n on server 1: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn >
2015 Jun 20
2
Duplicate mails with pop3 + dsync replication
Hi, When I enable (and it only happens when it is actually running) replication over TCP my users get duplicate mails via pop3. Here?s what happens: * User gets mail * Mail appears in (Maildir) new/ folder on both replicas * user retrieves mail (retr), calls dele. Mail still exists in new/ folder on both replicas. * user runs retr (and gets the duplicate) and dele a second time, the mail is
2015 Jun 21
0
Duplicate mails with pop3 + dsync replication
FWIW I just tried the sdbox mailbox format for a singe user (not the whole installation) by overriding the mail-userattr via ldap and the problem persists, so I don?t think it?s an issue with maildir per se, but rather a pop3 / replication issue or a misconfiguration on my side. Wolfgang > On 20 Jun 2015, at 22:29, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > Hi, >
2015 Jun 22
2
Duplicate mails with pop3 + dsync replication
It turns out that if I enable this option: pop3_deleted_flag = "$POP3Deleted? The issue no longer persists. I have to manually expunge the kept mails that have been deleted via pop3 though: doveadm expunge mailbox INBOX KEYWORD '$POP3Deleted' -A Wolfgang > On 21 Jun 2015, at 21:05, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > FWIW I just tried the sdbox
2020 Oct 12
0
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div class="default-style"> Replication is not supported with mbox format. You can only do unidirectional sync out of mbox. </div> <div class="default-style"> <br> </div> <div
2015 Mar 01
0
dsync panic
As per <http://wiki2.dovecot.org/Migration/Dsync>, I'm running the following command on a local dovecot server to replicate email for a single user from a remote IMAP server: doveadm -D \ -o imapc_host=remote.imap.server \ -o imapc_user=gcr \ -o imapc_password=XXXXXXXX \ -o imapc_list_prefix=IMAP \ -o imapc_features="rfc822.size fetch-headers" \ -o
2018 Mar 30
1
Replication fails with dsync-server(admin@asergis.com): Error: Couldn't create lock /home/admin/.dovecot-sync.lock: No such file or directory
Hello I have configured replication using dsync. It fails with a message Error: Couldn't create lock /home/admin/.dovecot-sync.lock: No such file or directory This directory predictably does not exist - all my users are supposed to be virtual.? I can not find an option to switch this off. At the same time if I try manual replication I get segfault error Mar 30 17:17:24
2020 Oct 11
2
Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
I am preparing a bit for setting up replication. However when I manually try to dsync an account, the first time I execute this[1] command it seems to be ok. The 2nd time I am getting this error[2]. If I add -1 (one way syncing) the error disappears. Does this mean I will have problems with setting up replication between these two servers? [1] [@ ~]# doveadm sync -n inbox -u testaccount
2020 Jul 16
0
Variable expansion in passwords
Hello list A user reports failure to log in after password change. The client side error message indicates a lost or dropped connection by the server. A peek into the server logs reveales this: dovecot: imap(user at example.com)<53267><el0HoZGqHIdb0K2G>: Error: Failed to expand plugin setting plain_pass = 'asdf%?asdf': Unknown variable '%?' This looks a lot like a
2018 Jan 15
2
Duplicate mail id issue, mailbox does not exist when dovecot tries to generate a new guid so replication can take place
Hi all, When we run the below one user constantly shows as failed (dovecot version is 2.2.13): sudo doveadm replicator status "*" mail.log shows the below for the user: Jan? 3 16:20:57 hostname dovecot: dsync-server(user): Error: Duplicate mailbox GUID <guid number> for mailboxes <mailbox name.sub folder> and <mailbox name.sub folder> - giving a new GUID <guid
2020 May 25
3
child killed by signal 6
Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my telnet session might help: a11 fetch 1 all * 1 FETCH (RFC822.SIZE 16750 INTERNALDATE
2014 Sep 02
0
dsync-server couldn't create .dovecot-sync.lock file
My dovecot stores users' emails on /var/spool/imap/<user> and stores the messages index on /var/lib/imap/<user>. I have many users who do not yet have their userdb_home directories created on the server, because that is created at the time of first login. I'm testing dsync for replication and have seen the following error: dsync-server(<user>): Error: Couldn't
2020 Jun 13
2
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hi, I've been seeing errors logged for some time with replication processes, whereby replication sessions seem to be timing out periodically. This is with dovecot version 2.3.10.1 (a3d0e1171) and both are Gentoo x86_64. After some investigation I've determined that these timeouts are only ever occurring with tcps as the replication connection type. These errors never occur if
2014 Aug 26
0
Running dsync results in Panic: file mbox-lock.c: line 799 (mbox_lock)
Hello, I'm converting our system to use dovecot. As part of the migration we need to convert existing mbox'es to Maildir format. I'm using latest Dovecot2 available as FreeBSD pkg - 2.2.13. I'm trying to use dsync, which results in: ./dsync -vfu ppaczyn -o mail_location=mbox:~/mail:INBOX=/var/mail/ppaczyn mirror maildir:~/Maildir dsync(ppaczyn): Panic: file mbox-lock.c: line 799
2009 Apr 22
1
smbclient fails when LDAP server is down
Hi all, I?m having some trouble setting up a samba failover scenario. This is what I?ve done: Subnet 192.168.1.0 -> Samba PDC e Samba BDC Subnet 192.168.20.0 -> LDAP Master e LDAP Slave If all servers are up I can login to domain. If I put the LDAP Master service down I am still able to login from the Slave LDAP. But if the server where the master LDAP is installed is down