search for: baplc

..."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.com:14...

...> > I have executed the command from the new server: > > > > ================================= > [root at production2 test.org.com <http://test.org.com/>]# doveadm backup -R -u kishore at test.org.com <mailto:kishore at test.org.com> remote:vmail at production1.baplc.com <mailto:remote%3Avmail at production1.baplc.com> > vmail at production1.baplc.com <mailto:vmail at production1.baplc.com>'s password: > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > altmove [-u <user>|-A] [-S <socket_...

...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.xxx,...

...> > I have executed the command from the new server: > > > > ================================= > [root at production2 test.org.com <http://test.org.com/>]# doveadm backup -R -u kishore at test.org.com <mailto:kishore at test.org.com> remote:vmail at production1.baplc.com <mailto:remote%3Avmail at production1.baplc.com> > vmail at production1.baplc.com <mailto:vmail at production1.baplc.com>'s password: > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > altmove [-u <user>|-A] [-S <socket_...

...xecuted the command from the new server: >> >> >> >> ================================= >> [root at production2 test.org.com <http://test.org.com/>]# doveadm backup -R -u kishore at test.org.com <mailto:kishore at test.org.com> remote:vmail at production1.baplc.com <mailto:remote%3Avmail at production1.baplc.com> >> vmail at production1.baplc.com <mailto:vmail at production1.baplc.com>'s password: >> usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] >> >> altmove [-u <user>|-A]...

...} mail_debug = yes verbose_ssl = no # Enable the replication plugin globally mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 } dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u plugin { mail_replica = remote:vmail at production3.baplc.com } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0600 user = vmail } } replication_max_conns = 10 imapc_host = producti...

...> > > > > > > > > > > > > > > > > > > > ================================= > > > > > > [root at production2?test.org.com (http://test.org.com/)]# doveadm backup -R -u?kishore at test.org.com?remote:vmail at production1.baplc.com > > > > > > vmail at production1.baplc.com's password: > > > > > > usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] > > > > > > > > > > > > altmove [-u <user>|-A] [-S <socket_path&gt...

...from the new server: >>> >>> >>> >>> ================================= >>> [root at production2 test.org.com <http://test.org.com/>]# doveadm backup -R -u kishore at test.org.com <mailto:kishore at test.org.com> remote:vmail at production1.baplc.com <mailto:remote%3Avmail at production1.baplc.com> >>> vmail at production1.baplc.com <mailto:vmail at production1.baplc.com>'s password: >>> usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] >>> >>> altmove [-u...

...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 old box. If so, then per Kishore?s earlier posts, the machine where this is being attempted is running 2.0.9?not 2.2.36 Maybe nothing but thought I would mention it? > On Jul 27, 2020, at 2:5...

...0bfa63) The old version is : ====================== [root at production1 ~]# dovecot --version 2.0.9 I have executed the command from the new server: ================================= [root at production2 test.org.com]# doveadm backup -R -u kishore at test.org.com remote:vmail at production1.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> auth [-a <auth socket path>] [-x <auth info>] <user> [<pass...

...== > [root at production1 ~]# dovecot --version > 2.0.9 > > > I have executed the command from the new server: > > > > ================================= > [root at production2 test.org.com]# doveadm backup -R -u kishore at test.org.com > remote:vmail at production1.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> > auth [-a <auth socket path>] [-x <auth info>...

...0bfa63) The New version is : ====================== [root at production1 ~]# dovecot --version 2.0.9 I have executed the command from the new server: ================================= [root at production2 test.org.com]# doveadm backup -R -u kishore at test.org.com remote:vmail at production1.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> auth [-a <auth socket path>] [-x <auth info>] <user> [<pass...

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> auth [-a <auth socket path>] [-x <auth info>] <user> [<pass...

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

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

...ectory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 html_directory = no inet_interfaces = testserver.baplc.com inet_protocols = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost myhostname = localhost newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory...

I am using pop3/imap, see the below file. We can't verify any logs? This is working fine from last one year. as part of testing we just stopped the services for 20minutes and restarted the dovecot and postfix server using "service <dovecot/postfix> stop/start". No issues so far... I would like know, if the application is reading the emails from the server, do we have any log