similar to: dsync not replicatiing .dovecot.sieve

Hi, Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical hosts. I recently noticed ".dovecot.sieve" and ".sieve/managesieve.sieve" are not replicating from one host to the other in either direction. Mail is having no trouble replicating on both hosts with dsync, it is only sieve files that are not replicating for unclear reasons. # doveconf -n host 1:

Hi, I'm using dovecot 2.3.2.1 on Xenial from upstream packages on two Dovecot servers connected with dsync over TCP. E-mails which are deleted via POP3 protocol are not correctly deleted on second server via dsync. Jul 25 09:29:19 mda11 dovecot: pop3(jakub@***)<7587><8xaJ1c1x9uEqAB7QADwAAAAAAAAAAL7v>: expunge: box=INBOX, msgid=<6a75db5d84ff257216a4340d7c0405b2 at

I think I get pretty much the same issue: dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a]

Here is it # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.2 (5d6d7c92) # OS: Linux 4.4.0-112-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: mda22 auth_cache_negative_ttl = 2 secs auth_cache_size = 16 M auth_cache_ttl = 1 mins auth_master_user_separator = / auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 default_process_limit = 2000

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2):

Hi all, To backup our imap folders I've a cronjob running in the night: /usr/bin/doveadm -o stats_writer_socket_path= backup -R -A -N tcp:xxx.yyy.zzz:4191 This ran successful when I set it up and didn't look at it anymore. Recently I noticed errors: dsync-local(administration)<uO/qHjXS6FteLAAA3i05xw>: Panic: file dsync-mailbox-tree-sync.c: line 1253 (sync_create_mailboxes):

Can you try enabling mail_debug=yes, perform a pop3 session and provide logs? Aki On 25.07.2018 15:53, Jakub L?nsk? wrote: > Here is it > > # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.2 (5d6d7c92) > # OS: Linux 4.4.0-112-generic x86_64 Ubuntu 16.04.4 LTS > # Hostname: mda22 > auth_cache_negative_ttl = 2 secs > auth_cache_size = 16 M >

Hi All, So close and yet so far.? ;-( Have been migrating users from an old Dovecot server to a new one. All of the users have doveadm backup'd perfectly, except for one ! What does the below mean ? $ sudo doveadm -v -o imapc_user=jd at example.org.tld -o imapc_password=secretSquirrel -o imapc_host=old-server.example.com backup -1 -R -u jd at example.org.tld imapc: dsync(jd at

Having dsync to make backups from existing mail-spaces, it would be nice to make dsync syncing the sieve-dirs too. -Otherweise backups aren't complete... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht

Hi there, I am currently doing some extensive test with dsync, but it appear that : dsync -u <user> maildir:/path/to/new/Maildir doesn't seems to sync sieves rules. Is there a good way to sync sieves as well ? :p Regards, Xavier

Hi, Introduction: There are two domains, for example (aaa.com, bbb.com). In the aaa.com domain two users (bob at aaa.com, alex at aaa.com). In the bbb.com domain there are no users. In time full sync replication (replication_full_sync_interval) operations in logs appear errors: dovecot: dsync-local(bob at aaa.com): Error: Mailbox INBOX: Failed to set attribute

Hi all i'm migrating a cyrus imapd server to dovecot with dsync everyting seems working but sieve rules are not copied to dovecot server I searched for documentation but without any luck I use the configuration below with doveadm -v -o mail_fsync=never backup -R -u emailaddr imapc: Is sieve supported with dsync? How I can specify sieve server address and port? # 2.2.13.21 (606efd4a4f35):

Hello, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get replicated to the other - great! However, if I set a script to be active (SETACTIVE) on one side then this is not being replicated across to the other

Hi, What are people doing for backups ? My current process is LVM snapshot and backup from that to NFS share. But there seems to be hints around the internet that people use/abuse "doveadm backup" for backup purposes even though it seems its original intention was for transferring mailboxes between dovecot instances. Assuming its ok to "doveadm backup" to an NFS share, is it

I?d like to migrate to a new server. I only need to transfer the mail store, have already done the users. I?ve seen different recommendations: IMAP-Sync Rsync Doveadmin backup and dsync What are the pros and cons of each? What would be best for me? I?m thinking that Doveadmin backup is the way to go. Both old and new servers are on same network. New server is running Dovecot 2.3.2.1, old server

Hello, I have compiled Dovecot 2.3.3 from sources but I have problems with authentication. I tried to rebuild Dovecot 2.3.2.1 but the error persists. I attach a .txt file with the information requested to report a bug. My main mail server is fallen, (the same for the test server) I will send the report from a Gmail address. If you need additional information I will be at your disposal.

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

On Thursday, October 11, 2018 1:29 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 11 October 2018 at 15:02 Laura Smith n5d9xq3ti233xiyif2vp at protonmail.ch wrote: > > > > > That's a permission error. Somewhere in your directory hierarchy things > > > are off. See Postfix' set-permissions command. > > > > But surely if Dovecot

Hi, Going by the "static userdb" example? on this page (https://wiki.dovecot.org/VirtualUsers#homedirs), tried to achieve a similar setup in conjunction with pgsql for passdb. However I get an error "auth: Warning: sql: Ignoring changed iterate_query in /etc/dovecot/local_sql_users.conf, because userdb sql not used. (If this is intentional, set userdb_warning_disable=yes)"

> That's a permission error. Somewhere in your directory hierarchy things > are off. See Postfix' set-permissions command. > But surely if Dovecot is staring as root then directory permissions are relevant, especially if I'm then asking the config to chmod the file anway ? To me, it seems dovecot is not behaving correctly, because if it is not using root to access the