similar to: doveadm backup for all users to file system

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot:

Hi, according to the man page doveadm-backup, the verbosity switch "-v" should do the following: "Enables verbosity, including progress counter" However, i see no difference running the following command with or without the "-v" switch: >>doveadm -v backup -R -A remote:myhost The command itself works without problem, two mailboxes are correctly

Hi! I test dsync through tcp. In a log error: dsync-remote (): Error: doveadm client: No command given All are synchronized. The error is shown by rand for the user and on that server where it is synchronized # 2.2.rc2 (976bf9e69367): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.6 ext3 auth_mechanisms = plain login digest-md5 auth_username_format = %Ln@%Ld

Hi folks, Not sure how much extra information I'll be able to provide on this, but I'm experiencing a consistent, reproducible dsync backup error with a single, specific account I'm trying to migrate from UW-IMAP / Panda (mix mailbox) to a Dovecot 2.2.32 cluster. Didn't spot any core files laying around. Doveadm backup output, dovecot --version and dovecot -n below:

Hello Timo, I'm experimenting with 'doveadm backup' on 2.1.1 (latest hg, full dovecot -n output attached) and haven't managed to get it working. This is what I have done: 1. Create the directory /tmp/backup which is empty 2. Run doveadm -v backup -u testuser at ubuntu-test.localdomain mdbox:/tmp/backup/ Then I see the following errors: doveadm -v backup -u testuser at

Hello! I'm using 2 namespaces, "inbox" for INBOX and it's subfolders and "special" containing folders like Sent, Junk or Drafts.??Though both use mdbox I decided to represent those namespaces in different locations "mdbox:~/mail" and "mdbox:~/mail_special_folders". The main reason to use 2 namespaces was to keep special_use folders out of INBOX by

This is probably problem on the other end. Aki On 20.11.2017 19:36, Dovecot list wrote: > Hello. I try to migrate dovecot 1 to dovecot 2 with doveadm backup. > But when i try to set doveadm backup i get : > > mx3:/root/dsync@[23:11] # doveadm -v -c ah.temp backup -R -u ah at test.pl > <ahuryn at i-pi.pl> imapc: > doveadm(ah at test.pl <ahuryn at i-pi.pl>): Error:

Hi, FWIW this was also reported back in August[1] - experienced with 2.3.2.1 (not sure if earlier 2.3 releases were affected) and currently reproducible with latest 2.3.3 stable release. [1] https://www.dovecot.org/pipermail/dovecot/2018-August/112548.html Cheers, Tony On 2018-10-12 04:26, Pascal wrote: > Hello, > > I use dovecot replication and the sieve scripts are not

Until today I could do this to backup my primary IMAP4 server: """ doveadm backup ssh csi doveadm dsync-server """ It doesn't work anymore after upgrading to Dovecot 2.2.18: """ jcea at ubuntu:~$ doveadm backup ssh csi doveadm dsync-server Enter passphrase for key '/home/jcea/.ssh/id_rsa': dsync-remote(root): Error: Mailbox INBOX: Failed

Hi, i try to migrate mails from a non dovecot imap server to a dovecot imap server with doveadm backup as described there: http://wiki2.dovecot.org/Migration/Dsync i first tried (local-mailbox port 18143 is the non dovecot imap server): /usr/bin/doveadm -o imapc_user=user at example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -o

Good morning, I use ?doveadm backup -R -m foo -s $state? to create a local mirror of an imapc remote folder. When I run that command, wait for it to finish, deliver a new message to the remote folder, and run that command again, the new message does not get downloaded from the remote. I'll attach the rawlog, doveconf, etc at the end. Allow me first to summarize what I've already

Most documents around there talk abour "dsync", but the modern way is "doveadm backup". This command is not documented in the wiki and there are a few details missing, like how to use it thru SSH. I am currently doing some tests about how to backup my mdbox. I can do tests in local using: $ doveadm backup -u jcea -m proveedores/dovecot mdbox:/tmp/aa/ This will

Hello again, I am still stuck I'm afraid. I now have doveadm backup working perfectly from a small gmail mailbox (a few hundred messages), but when I try the same configuration (apart from usernames and passwords obviously) with a large gmail mailbox (around 60,000 messages), doveadm connects successfully, replicates the gmail folder tree, then produces no further output until about 30

2.2.13/0.4.2, both from source-tarball, no fancy options. tcp-replication between two nodes and following plugin parameters (same on both sides, except the ip-addr) plugin { sieve_before = /home/ssfn/etc/dovecot/sieve.default sieve_global_dir = /home/ssfn/etc/dovecot sieve = ~/.dovecot.sieve sieve_dir = ~/.sieve sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 6h

I'm not clear myself on the difference myself between dsync doveadm sync doveadm dsync-server ... perhaps someone here can explain? However what worked for me was using doveadm dsync-server on the 'receive' end. Maybe that puts it in 'listen' mode? So maybe try doveadm backup -u user at abc.net \ ssh root at po.abc.net \ docker exec b3093cxxxxxx doveadm dsync-server -u

> On 30/03/2020 22:11 Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > > I am trying to backup a gmail account (not the one I am writing from) > to dovecot, using doveadm-backup and imapc, but am having ssl > connection problems. > > ted at expectation:~# doveadm backup -D -R -u ted imapc: > dsync(ted): Info: imapc(imap.gmail.com:993): Connected to >

On 9/2/19 3:03 PM, Sami Ketola wrote: >> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: ... >> Is there anyway for dsync to avoid moving Gigabytes of data for could >> just be "moved" by moving the mount? > > > Not tested but you can probably do something like this in the target server: > > doveadm backup -u

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

I struggled with this at one time, and with the lack of examples around the internet. In fact, I might have written this very post myself at one point! In the end, the penny dropped when I saw that the format was (command on local server) + (stuff you need to connect over ssh) + (command on remote server) So what worked for me was: doveadm backup -u user at domain.com \ ssh -p 2222 (+ other

Sorry for being such a newbie when it comes to scripting. Created a directory for the backups on the network mounted volume. Changed the appropriate path and am getting this: dsync(root): Error: user nfsnobody: Initialization failed: Namespace 'INBOX.': mkdir(/mnt/maelstrombackups/vmailbackup/nfsnobody) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: