similar to: doveadm sync -1 -R

According to doveadm-dsync man page the above two options are valid, but they are rejected when used: tornado # doveadm backup -v -u testuser remote:pi.me.name:4814 backup: invalid option -- 'v' doveadm backup [-u <user>|-A] [-S <socket_path>] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x

Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say ?production1??I just double-checked as well... FWIW?the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above? Here you appear to be exec?ing the command on prod2 and trying to pull from the remote of prod

Not sure if this matters but the prompt when attempting the ?doveadm backup? command shows it to be a ?production" server? [root at production1 <https://dovecot.org/mailman/listinfo/dovecot> test.org.com]# doveadm backup -R -u kishore at test.org.com <https://dovecot.org/mailman/listinfo/dovecot> remote:vmail at production2.baplc.com

Hi folks, I have an old server running qmail with several years of mails in maildir format I want to migrate to a new server, without requiring fresh client download of everything. Old server is debian 6(?). Local IP is 192.168.0.1. New server is Debian 10, local IP is 192.168.0.25. I have dovecot 2.3.4.1 (latest from apt stable) installed and apparently working - if I manually copy the home

Yes. Please find the details of the servers below. I am executing the command from one of the new servers. My Current Production Server details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6 ======================== New Servers: ========================== Linux OS - Red Hat Enterprise

Well that option set still doesn?t look correct? Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36? [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm [Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f

I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side. Do you have dsync on the 2.0.9 machine? > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > This is what my understanding. May be I am also wrong here. > > Backup option

> On 30. Jul 2020, at 19.33, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > >> >> On 30/07/2020 19:29 Justin Coleman <jmcoleman at gmail.com> wrote: >> >> >> Hi folks, >> I have an old server running qmail with several years of mails in maildir format I want to migrate to a new server, without requiring fresh client download of

Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } This should

Hi! We have 2 servers replicating each other and after upgrade to 2.2.26.0 we are seeing this in the logs: Primary server: Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user at domain.ee): Panic: file dsync-brain-mailbox.c: line 814 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0)

A question for the best winbind SID-UID/GID mapping in our situation: I'm building a new infrastructure with Windows 2003SP1 ADS Domaincontrollers and some Debian Servers (File: Samba+NFS; Mail; Web; ....) and varios XP and Debian Clients. After reading Chapter 12. (Identity Mapping) in the Samba-HOWTO is IDMAP_RID in couple with winbind an easy way to solve the problem with syncr.

Hi Folks, I was wondering if I could ask this question here. Initially when I was thinking up how to do this I was expecting block encryption to stay consistent from one 'encryption run' to the next, but I found out later that most schemes randomize the result by injecting a random block or seed at the beginning and basing all other encrypted data on that. In order to prevent

Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see

Hello everybody, I have a matrix with measurement values and plot them with persp. I want to highlight different heights in different colors. At least everything above and under a certain z-level shall have a different color to make the differences in height more obvious. How can I do that or do I have to use another package? Best regards, Juliane

All this talk about SATA RAID in the past few days made me wonder... about possibly using software RAID, or at least trying it on my own workstations and eventually production servers, after I learn more about it. So, I started googling for tutorials and manuals, and there are usually two kinds I can find: 1. very basic "what is software RAID", or 2. complete 400+ page books on the

I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing. The old version is: ==================== [root at

I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > upgrading to 2.3.9

Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's. The new version is: ==================== [root at production2 ~]# dovecot --version 2.2.36 (1f10bfa63) The old version is : ====================== [root at production1 ~]# dovecot

Hi, But there is no "doveadm backup" option in dovecot 2.0.9 version. [root at production ~]# doveadm -backup doveadm: invalid option -- 'b' [root at production ~]# dovecot --version 2.0.9 Copy the contents by using "scp", will that work? Thanks, Kishore Potnuru On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >

Hi I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions. My Current Production Server details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9