search for: production1

...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 to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore at test.ba.com): Warning: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore at test.ba.com): Info: imapc(production1.baplc....

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 1?your earlier post was exec?ing on prod1 and pullin...

...h>] [-1] [<user mask>] [<ip/bits>] zlibconnect <host> [<port>] > On Jul 27, 2020, at 3:28 PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > 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 : > ====================== &...

...PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > 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. > > Kishore > > On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, <tech at leding.net <mailt...

...> > > > > > > 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. > > > > > > Kishore > > > > > > > > > On M...

...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 <mailto:kishore at test.ba.com> imapc: > dsync(kishore at test.ba.com <mailto:kishore at test.ba.com>): Info: imapc(production1.baplc.com:143 <http://production1.baplc.com:143/>): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) > dsync(kishore at test.ba.com <mailto:kishore at test.ba.com>): Warning: imapc(production1.baplc.com:143 <http://production1.baplc.com:143/>): connect(xxx.xxx.xxx...

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 <https://dovecot.org/mailman/listinfo/dovecot> ...that would seem to me to indicate the...

...ore.reachme at gmail.com>> wrote: >> >> 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. >> >> Kishore >> >> On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, <tech...

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 master = yes pass = yes }...

Hi All, I have tried the below command to migrate the data from the old server(dovecot version: 2.0.9) to new servers(dovecot version: 2.2.36 (1f10bfa63)). But it's throwing an error. old server name: production1 new server1 name: production2 (for HA/Replication) new server2 name: production3 (for HA/Replication) I have configured replication between production2 and production3, which is working fine. The issue is, the below command I am trying is from production2 server and trying to take the data from...

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 --version 2.0....

...uth: Fatal: Master passdb can't have pass=yes if there > are > > no passdbs > > Jul 28 11:14:23 master: Error: service(auth): command startup failed, > > throttling > > =============== > > > > after the above error, I have commented "pass=yes" in production1 (old > > server) server, then I see the below error. > > > > ================ > > Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. > > PLAIN mechanism needs one > > Jul 28 11:17:10 master: Error: service(auth): command startup failed, >...

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. Kishore On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, <tech at leding.net> wrote: > Well that option set st...

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 gettin...

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 production2 ~]# dovecot --version 2.2.36 (1f10bfa63)...

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] [-S <socket_path>] <search query&...

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 production1.testorg.com 143 Thanks and regards Markus

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

...============ > Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are > no passdbs > Jul 28 11:14:23 master: Error: service(auth): command startup failed, > throttling > =============== > > after the above error, I have commented "pass=yes" in production1 (old > server) server, then I see the below error. > > ================ > Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. > PLAIN mechanism needs one > Jul 28 11:17:10 master: Error: service(auth): command startup failed, > throttling > =============...

Hi Kishore, On 04.08.20 09:50, Kishore Potnuru wrote: > So, both password?files (master and regular user credentials) have the same > contents in this scenario, correct? first of all: thanks for collecting the information. As Joseph wrote: I too think that in your config of 'production1' a passdb with the credentials of regular users is missing. On one of my servers I'm using this: passdb { driver = passwd-file master = yes args = /etc/dovecot/master-users #pass = yes } passdb { driver = passwd-file args = username_format=%u /etc/dovecot/users } Som...