similar to: Migrating from qmail server, invalid option "o" in dsync

Displaying 20 results from an estimated 800 matches similar to: "Migrating from qmail server, invalid option "o" in dsync"

2020 Jul 30
2
Migrating from qmail server, invalid option "o" in dsync
> 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
2020 Jul 30
0
Migrating from qmail server, invalid option "o" in dsync
Maybe I'm misunderstanding - all of our clients use pop3 (thunderbird and eudora). Do pop3 and imap overlap somehow, or does the server use IMAP internally regardless of the client protocol settings? Thanks! On Thu, Jul 30, 2020 at 12:52 PM Sami Ketola <sami.ketola at dovecot.fi> wrote: > > > On 30. Jul 2020, at 19.33, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
2020 Jul 30
0
Migrating from qmail server, invalid option "o" in dsync
> 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 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.
2015 Apr 30
1
doveadm -D and -v options
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
2020 Jul 27
2
Migration from one server to 2 new servers
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
2019 Sep 30
2
courier to dovecot migration
> > >> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >> wrote: >>> >> WOW! - amazing quickly, I'm really grateful. >> >> I was using: -u tovis imapc: nusi but still something wrong. >> Patstebin: https://pastebin.com/tH4wzJka >> The most relevant part (I think) is: >>
2019 Sep 30
2
courier to dovecot migration
> > On 30.9.2019 12.38, tovises wrote: >>> On 29.9.2019 23.38, tovises via dovecot wrote: >>>> I have a quite old home server based on Debian 6.x packages using >>>> courier >>>> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >>>> my >>>> and my wife emails (about 25G). >>>> I want renew
2020 Jul 27
2
Migration from one server to 2 new servers
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
2013 Sep 02
1
migration from IMAP/POP3 courier server to a remote dovecot server
Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read
2020 Jul 27
3
Migration from one server to 2 new servers
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
2019 Sep 29
2
courier to dovecot migration
I have a quite old home server based on Debian 6.x packages using courier imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep my and my wife emails (about 25G). I want renew my server to Debian 10 (buster) and got a recommendation to use dovecot instead of courier. For this purpose I'm using a different PC as a sandbox. Debian 10 currently offer dovecot version 2.3.4.1
2019 Sep 30
2
courier to dovecot migration
> > On 30.9.2019 13.40, tovises wrote: >>> >>>> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >>>> wrote: >>>> WOW! - amazing quickly, I'm really grateful. >>>> >>>> I was using: -u tovis imapc: nusi but still something wrong. >>>> Patstebin: https://pastebin.com/tH4wzJka
2019 Sep 30
2
courier to dovecot migration
> > On 29.9.2019 23.38, tovises via dovecot wrote: >> I have a quite old home server based on Debian 6.x packages using >> courier >> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >> my >> and my wife emails (about 25G). >> I want renew my server to Debian 10 (buster) and got a recommendation to >> use dovecot instead of
2015 Dec 02
1
doveadm backup -R
We're using doveadm -o imapc_user="$USER" -o imapc_password="$PASSWORD" -o imapc_host=$SERVER1 -o pop3c_user="$USER" -o pop3c_password="$PASSWORD" -o pop3c_host=$SERVER1 -D -v backup -R -u "$USER" imapc: to migrate Mails from Courier to Dovecot. We have some complaints on the old system that there are changes on the old system where
2015 Apr 09
1
gmail-migration: archived mails in \ALL
Hi, I don't completly understand http://wiki2.dovecot.org/Migration/Gmail I can't find the documentation for the -a and the -F Flag. I'd like to migrate ONLY archived mails from an existing gmail-Account. So I'd have to import all Mails from the \ALL-Folder that does NOT have any virtual folder flags set. I tried to use this command: doveadm -D -o imapc_user=user at
2014 Jan 31
1
dsync Error: Mailbox INBOX: Save commit failed: Mailbox was deleted under us
Hi, I am doing a mass migration of users from Cyrus imap on a solaris server to dovecot 1:2.2.9-1ubuntu1 and am getting this weird issue with dsync if I try to do a "full" sync. Debug output below: dsync(user at example.com): Error: Mailbox INBOX: Save commit failed: Mailbox was deleted under us dsync(user at example.com): Debug: brain M: out box 'INBOX'
2019 Jul 26
2
doveadm migration to server with no root access
Hi I am trying to do mailbox migrations using doveadm to a server that I do not have root access on without success. Is this possible? What I have done and results: ssh to server with mailboxes to copy and then su cp /etc/dovecot/dovecot.conf /root/tmp/dovecot_new.conf append text below** to end of dovecot_new.conf try to copy mail 3 different ways (all fail see error messages) doveadm -D -v
2020 Jul 27
2
Migration from one server to 2 new servers
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
2020 Jul 27
2
Migration from one server to 2 new servers
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
2020 Jul 28
2
Migration from one server to 2 new servers
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