similar to: Migration issue

Thank you for the reply. In old server (production1), I have changed like this for passdb. rest all i kept the same. passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes #pass = yes } passdb { driver = passwd-file args = username_format=%u /etc/dovecot/passwd } Now I am getting the below Authentication error from

Thank you for the response. So, both password files (master and regular user credentials) have the same contents in this scenario, correct? -Kishore On Mon, Aug 3, 2020 at 11:42 PM Joseph Tam <jtam.home at gmail.com> wrote: > On Mon, 3 Aug 2020, Kishore Potnuru wrote: > > > =============== > > Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there

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

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

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 Aki & Dovecot team, Just continuing with the previous discussion "Migration from one server to 2 new servers". Hi, I have tried the same way as per your suggestion. But it's throwing an error. ------------- [root at production2 log]# doveadm backup -a All -R -u kishore at test.ba.com imapc: dsync(kishore at test.ba.com): Info: imapc(production1.baplc.com:143): Connected

Adding the dovecot.conf configuration from old and new servers: ========================================= My old server dovecot.conf (production1): ========================================= disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/z1dev/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file

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 Kishore, On 03.08.20 15:33, Kishore Potnuru wrote: > Please let me know if you need any other details. please provide the following outputs/answers: 1) Are users able to login and access their mailboxes on production1 with an IMAP client? On your old server (production1): 2) ps aux | grep dovecot 3) netstat -lntp 4) ls -la /etc/dovecot On your new server (production2): 5) telnet

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

Hey Kishore? I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the ?Next\Previous message? links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here: https://dovecot.org/list/dovecot/2012-February/133718.html

This is what my understanding. May be I am also wrong here. Backup option is there in my new server, production2. When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same. Sorry just incase if I am wrong.

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

Not sure if this is the issue but the error says no password database is cfg?d?is that truly the case? Maybe post a redacted config for the community to review? > On Jul 28, 2020, at 7:20 AM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > Hi Aki & Dovecot team, > > Just continuing with the previous discussion "Migration from one server to 2 new

Hi All, I have 2 test servers with the below configuration. ========================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 ========================== Trying to create High Availability. I have added both of the above servers behind a F5 load balancer. I have got a Load Balancer FQDN

Hi , I have tried the below command from the new server. But I am getting an error. Anything is missing here? ======== [root at production1 test.org.com]# doveadm backup -R -u kishore at test.org.com remote:vmail at production2.baplc.com vmail at production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A]

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

Thank you for the reply. I have done the sync manually with "doveadm sync" command. But, I have not configured the replication yet. I am looking at the below webpage for the replication. https://wiki.dovecot.org/Replication I am using the dovecot version "2.2.36". I am confused with what needs to be done after reading that page. 1. They are talking about v2.3.1 and v2.2+.

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: > > >