Re: Migration dovecot server with local users to dovecot with virtual mailboxes

[t Seeger]

Paul thx for your time and help!

After a long time of testing i noticed something... probably a small thing
for a dovecot expert...
The seen mails of the old server have a ",S" at the end of the filename.
The seen mails of the new server have a ",:2,S". If I rename the mails
before the import, they are also shown as seen after the import.

Old:
Maildir/cur/1686401814.M960194P17178.post,S=7095,W=7251%3A2,S

New:
Maildir/cur/1686401814.M960194P17178.post,S=7095,W=7251%3A2,:2,S

Is it possible to set an option at the old server, that new mails are
marked with ",:2,S" or at the new one. Or would a update of the old server
to a newer version help? The current version of the old server is "2.3.4.1"

Best regards
Thorsten

On Fri, Jun 9, 2023 at 1:31 PM Paul Kudla (SCOM.CA Internet Services Inc.) <
p...@scom.ca> wrote:

>
> ok i went through this and the best solution although it is a bit of work
>
> is imapsync
>
>
> imapsync --host1  --user1 --password1 \
>
> --host2 --user2 --password2 \
>
> --regextrans2 "s,\.,_,g"
>
> see : https://github.com/imapsync/imapsync
>
> note the reg parameter above deal with dot in mailboxes etc
>
> virtual mail requires a database of user data, i made a python script to
> step through all the account to sync to the new servers.
>
>
> It basically deals with the compatibility issues between servers.
>
>
>
>
> Happy Friday !!!
> Thanks - paul
>
> Paul Kudla
>
>
> Scom.ca Internet Services 
> 004-1009 Byron Street South
> Whitby, Ontario - Canada
> L1N 4S3
>
> Toronto 416.642.7266
> Main 1.866.411.7266
> Fax 1.888.892.7266
> Email p...@scom.ca
>
> On 2023-06-09 6:51 a.m., t Seeger wrote:
> > Thank you for the link, unfortunately I am missing the crucial clue. I
> > get the directories backed up, but I don't get them imported
> > properly all mails are displayed as unseen. i tried with simple
> > pasting and the doveadm import command. Is there a trick to preserve the
> > flags? Maybe it is because the old dovecot server uses short username
> > without the @ and the domain name and the new one uses the mail address
> > to identify the user.
> >
> > On Thu, Jun 8, 2023 at 3:26 PM aki.tuomi via dovecot
> > mailto:dovecot@dovecot.org>> wrote:
> >
> > Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/
> > 
> >
> > Aki
> >
> >  Original message 
> > From: tseeger...@gmail.com 
> > Date: 6/8/23 16:10 (GMT+02:00)
> > To: dovecot@dovecot.org 
> > Subject: Migration dovecot server with local users to dovecot with
> > virtual mailboxes
> >
> > Hello,
> > we are using a dovecot server with NIS, we want to transfer it to a
> > new setup. As backend a mysql server will be used in the future.
> > My problem is, if I just copy the maildir or use "doveadm import"
> > all mails are flagged as "unseen". How can i preserve the flags?
> >
> > This is how I have tried it so far.
> > root@mail / $ doveadm import -s -u testuser@testdomain.local
> > maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"
> >
> > As a "workaround" I tried to change the flags.
> > root@mail / $ doveadm -v flags add -u testuser@testdomain.local
> > "Seen" "ALL"
> > This led partially to the desired success, the mails are shown as
> > "seen", but the folders (e.g. Roundcube) still show unread mails.
> >
> > dovecot -n
> > 
> > # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
> > # Pigeonhole version 0.5.13 (cdd19fe3)
> > # OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7
> > # Hostname: mail.testdomain.local
> > auth_mechanisms = plain login
> > mail_fsync = always
> > mail_gid = vmail
> > mail_home = /var/vmail/mailboxes/%d/%n
> > mail_location = maildir:~/mail:LAYOUT=fs:INDEX=MEMORY
> > mail_privileged_group = vmail
> > mail_uid = vmail
> > managesieve_notify_capability = mailto
> > managesieve_sieve_capability = fileinto reject envelope
> > encoded-character vacation subaddress comparator-i;ascii-numeric
> > relational regex imap4flags copy include variables body enotify
> > environment mailbox date index ihave duplicate mime foreverypart
> > extracttext imapsieve vnd.dovecot.imapsieve
> > mmap_disable = yes
> > namespace inbox {
> >inbox = yes
> >location =
> >mailbox Drafts {
> >  auto = subscribe
> >  special_use = \Drafts
> >}
> >mailbox Sent {
> >  auto = subscribe
> >  special_use = \Sent
> >}
> >mailbox Spam {
> >  auto = subscribe
> >  special_use = \Junk
> >}
> >mailbox Trash {
> >  auto = subscribe
> >  special_use = \Trash
> >}
> >prefix =
> > }
> > passdb {
> 

Re: Migration dovecot server with local users to dovecot with virtual mailboxes

[Aki Tuomi via dovecot]

Also came to mind that if you have the maildirs in place, you can just point 
dovecot to those maildirs, there is no need to import/convert them. 

Aki

> On 09/06/2023 14:08 EEST Aki Tuomi via dovecot  wrote:
> 
>  
> Yes, the trick is to use doveadm sync/backup, not doveadm import, as the 
> guide explains.
> 
> Aki
> 
> > On 09/06/2023 13:51 EEST t Seeger  wrote:
> > 
> > 
> > Thank you for the link, unfortunately I am missing the crucial clue. I get 
> > the directories backed up, but I don't get them imported properly all 
> > mails are displayed as unseen. i tried with simple pasting and the doveadm 
> > import command. Is there a trick to preserve the flags? Maybe it is because 
> > the old dovecot server uses short username without the @ and the domain 
> > name and the new one uses the mail address to identify the user.
> > 
> > 
> > On Thu, Jun 8, 2023 at 3:26 PM aki.tuomi via dovecot  
> > wrote:
> > > Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/
> > > 
> > > Aki
> > > 
> > >  Original message 
> > > From: tseeger...@gmail.com
> > > Date: 6/8/23 16:10 (GMT+02:00)
> > > To: dovecot@dovecot.org
> > > Subject: Migration dovecot server with local users to dovecot with 
> > > virtual mailboxes
> > > 
> > > Hello, 
> > > we are using a dovecot server with NIS, we want to transfer it to a new 
> > > setup. As backend a mysql server will be used in the future. 
> > > My problem is, if I just copy the maildir or use "doveadm import" all 
> > > mails are flagged as "unseen". How can i preserve the flags?
> > > 
> > > This is how I have tried it so far.
> > > root@mail / $ doveadm import -s -u testuser@testdomain.local 
> > > maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"
> > > 
> > > As a "workaround" I tried to change the flags.
> > > root@mail / $ doveadm -v flags add -u testuser@testdomain.local "Seen" 
> > > "ALL"
> > > This led partially to the desired success, the mails are shown as "seen", 
> > > but the folders (e.g. Roundcube) still show unread mails.
> > > 
> > > dovecot -n
> > > 
> > > # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
> > > # Pigeonhole version 0.5.13 (cdd19fe3)
> > > # OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7 
> > > # Hostname: mail.testdomain.local
> > > auth_mechanisms = plain login
> > > mail_fsync = always
> > > mail_gid = vmail
> > > mail_home = /var/vmail/mailboxes/%d/%n
> > > mail_location = maildir:~/mail:LAYOUT=fs:INDEX=MEMORY
> > > mail_privileged_group = vmail
> > > mail_uid = vmail
> > > managesieve_notify_capability = mailto
> > > managesieve_sieve_capability = fileinto reject envelope encoded-character 
> > > vacation subaddress comparator-i;ascii-numeric relational regex 
> > > imap4flags copy include variables body enotify environment mailbox date 
> > > index ihave duplicate mime foreverypart extracttext imapsieve 
> > > vnd.dovecot.imapsieve
> > > mmap_disable = yes
> > > namespace inbox {
> > >  inbox = yes
> > >  location = 
> > >  mailbox Drafts {
> > >  auto = subscribe
> > >  special_use = \Drafts
> > >  }
> > >  mailbox Sent {
> > >  auto = subscribe
> > >  special_use = \Sent
> > >  }
> > >  mailbox Spam {
> > >  auto = subscribe
> > >  special_use = \Junk
> > >  }
> > >  mailbox Trash {
> > >  auto = subscribe
> > >  special_use = \Trash
> > >  }
> > >  prefix = 
> > > }
> > > passdb {
> > >  args = /etc/dovecot/dovecot-sql.conf
> > >  driver = sql
> > > }
> > > plugin {
> > >  imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve
> > >  imapsieve_mailbox1_causes = COPY
> > >  imapsieve_mailbox1_name = Spam
> > >  imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve
> > >  imapsieve_mailbox2_causes = COPY
> > >  imapsieve_mailbox2_from = Spam
> > >  imapsieve_mailbox2_name = *
> > >  quota = maildir:User quota
> > >  quota_exceeded_message = User %u has exhausted allowed storage space.
> > >  sieve = 
> > > file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve
> > >  sieve_before = /var/vmail/sieve/global/spam-global.sieve
> > >  sieve_global_extensions = +vnd.dovecot.pipe
> > >  sieve_pipe_bin_dir = /usr/bin
> > >  sieve_plugins = sieve_imapsieve sieve_extprograms
> > > }
> > > protocols = imap lmtp sieve
> > > service auth {
> > >  unix_listener /var/spool/postfix/private/auth {
> > >  group = postfix
> > >  mode = 0660
> > >  user = postfix
> > >  }
> > >  unix_listener auth-userdb {
> > >  group = vmail
> > >  mode = 0660
> > >  user = vmail
> > >  }
> > > }
> > > service imap-login {
> > >  inet_listener imap {
> > >  port = 143
> > >  }
> > >  process_min_avail = 1
> > >  service_count = 1
> > > }
> > > service lmtp {
> > >  unix_listener /var/spool/postfix/private/dovecot-lmtp {
> > >  group = postfix
> > >  mode = 0660
> > >  user = postfix
> > >  }
> > >  user = vmail
> > > }
> > > service managesieve-login {
> > >  inet_listener sieve {
> > >  port = 4190

Re: Migration dovecot server with local users to dovecot with virtual mailboxes

[Paul Kudla (SCOM.CA Internet Services Inc.)]

ok i went through this and the best solution although it is a bit of work

is imapsync


imapsync --host1  --user1 --password1 \

--host2 --user2 --password2 \

--regextrans2 "s,\.,_,g"

see : https://github.com/imapsync/imapsync

note the reg parameter above deal with dot in mailboxes etc

virtual mail requires a database of user data, i made a python script to 
step through all the account to sync to the new servers.



It basically deals with the compatibility issues between servers.




Happy Friday !!!
Thanks - paul

Paul Kudla


Scom.ca Internet Services 
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3

Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca

On 2023-06-09 6:51 a.m., t Seeger wrote:
Thank you for the link, unfortunately I am missing the crucial clue. I 
get the directories backed up, but I don't get them imported 
properly all mails are displayed as unseen. i tried with simple 
pasting and the doveadm import command. Is there a trick to preserve the 
flags? Maybe it is because the old dovecot server uses short username 
without the @ and the domain name and the new one uses the mail address 
to identify the user.


On Thu, Jun 8, 2023 at 3:26 PM aki.tuomi via dovecot 
mailto:dovecot@dovecot.org>> wrote:


Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/


Aki

 Original message 
From: tseeger...@gmail.com 
Date: 6/8/23 16:10 (GMT+02:00)
To: dovecot@dovecot.org 
Subject: Migration dovecot server with local users to dovecot with
virtual mailboxes

Hello,
we are using a dovecot server with NIS, we want to transfer it to a
new setup. As backend a mysql server will be used in the future.
My problem is, if I just copy the maildir or use "doveadm import"
all mails are flagged as "unseen". How can i preserve the flags?

This is how I have tried it so far.
root@mail / $ doveadm import -s -u testuser@testdomain.local
maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"

As a "workaround" I tried to change the flags.
root@mail / $ doveadm -v flags add -u testuser@testdomain.local
"Seen" "ALL"
This led partially to the desired success, the mails are shown as
"seen", but the folders (e.g. Roundcube) still show unread mails.

dovecot -n

# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7
# Hostname: mail.testdomain.local
auth_mechanisms = plain login
mail_fsync = always
mail_gid = vmail
mail_home = /var/vmail/mailboxes/%d/%n
mail_location = maildir:~/mail:LAYOUT=fs:INDEX=MEMORY
mail_privileged_group = vmail
mail_uid = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart
extracttext imapsieve vnd.dovecot.imapsieve
mmap_disable = yes
namespace inbox {
   inbox = yes
   location =
   mailbox Drafts {
     auto = subscribe
     special_use = \Drafts
   }
   mailbox Sent {
     auto = subscribe
     special_use = \Sent
   }
   mailbox Spam {
     auto = subscribe
     special_use = \Junk
   }
   mailbox Trash {
     auto = subscribe
     special_use = \Trash
   }
   prefix =
}
passdb {
   args = /etc/dovecot/dovecot-sql.conf
   driver = sql
}
plugin {
   imapsieve_mailbox1_before =
file:/var/vmail/sieve/global/learn-spam.sieve
   imapsieve_mailbox1_causes = COPY
   imapsieve_mailbox1_name = Spam
   imapsieve_mailbox2_before =
file:/var/vmail/sieve/global/learn-ham.sieve
   imapsieve_mailbox2_causes = COPY
   imapsieve_mailbox2_from = Spam
   imapsieve_mailbox2_name = *
   quota = maildir:User quota
   quota_exceeded_message = User %u has exhausted allowed storage space.
   sieve =

file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve
   sieve_before = /var/vmail/sieve/global/spam-global.sieve
   sieve_global_extensions = +vnd.dovecot.pipe
   sieve_pipe_bin_dir = /usr/bin
   sieve_plugins = sieve_imapsieve sieve_extprograms
}
protocols = imap lmtp sieve
service auth {
   unix_listener /var/spool/postfix/private/auth {
     group = postfix
     mode = 0660
     user = postfix
   }
   unix_listener auth-userdb {
     group = vmail
     mode = 0660
     user = vmail
   }
}
service 

Re: Migration dovecot server with local users to dovecot with virtual mailboxes

[Aki Tuomi via dovecot]

Yes, the trick is to use doveadm sync/backup, not doveadm import, as the guide 
explains.

Aki

> On 09/06/2023 13:51 EEST t Seeger  wrote:
> 
> 
> Thank you for the link, unfortunately I am missing the crucial clue. I get 
> the directories backed up, but I don't get them imported properly all 
> mails are displayed as unseen. i tried with simple pasting and the doveadm 
> import command. Is there a trick to preserve the flags? Maybe it is because 
> the old dovecot server uses short username without the @ and the domain name 
> and the new one uses the mail address to identify the user.
> 
> 
> On Thu, Jun 8, 2023 at 3:26 PM aki.tuomi via dovecot  
> wrote:
> > Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/
> > 
> > Aki
> > 
> >  Original message 
> > From: tseeger...@gmail.com
> > Date: 6/8/23 16:10 (GMT+02:00)
> > To: dovecot@dovecot.org
> > Subject: Migration dovecot server with local users to dovecot with virtual 
> > mailboxes
> > 
> > Hello, 
> > we are using a dovecot server with NIS, we want to transfer it to a new 
> > setup. As backend a mysql server will be used in the future. 
> > My problem is, if I just copy the maildir or use "doveadm import" all mails 
> > are flagged as "unseen". How can i preserve the flags?
> > 
> > This is how I have tried it so far.
> > root@mail / $ doveadm import -s -u testuser@testdomain.local 
> > maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"
> > 
> > As a "workaround" I tried to change the flags.
> > root@mail / $ doveadm -v flags add -u testuser@testdomain.local "Seen" "ALL"
> > This led partially to the desired success, the mails are shown as "seen", 
> > but the folders (e.g. Roundcube) still show unread mails.
> > 
> > dovecot -n
> > 
> > # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
> > # Pigeonhole version 0.5.13 (cdd19fe3)
> > # OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7 
> > # Hostname: mail.testdomain.local
> > auth_mechanisms = plain login
> > mail_fsync = always
> > mail_gid = vmail
> > mail_home = /var/vmail/mailboxes/%d/%n
> > mail_location = maildir:~/mail:LAYOUT=fs:INDEX=MEMORY
> > mail_privileged_group = vmail
> > mail_uid = vmail
> > managesieve_notify_capability = mailto
> > managesieve_sieve_capability = fileinto reject envelope encoded-character 
> > vacation subaddress comparator-i;ascii-numeric relational regex imap4flags 
> > copy include variables body enotify environment mailbox date index ihave 
> > duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve
> > mmap_disable = yes
> > namespace inbox {
> >  inbox = yes
> >  location = 
> >  mailbox Drafts {
> >  auto = subscribe
> >  special_use = \Drafts
> >  }
> >  mailbox Sent {
> >  auto = subscribe
> >  special_use = \Sent
> >  }
> >  mailbox Spam {
> >  auto = subscribe
> >  special_use = \Junk
> >  }
> >  mailbox Trash {
> >  auto = subscribe
> >  special_use = \Trash
> >  }
> >  prefix = 
> > }
> > passdb {
> >  args = /etc/dovecot/dovecot-sql.conf
> >  driver = sql
> > }
> > plugin {
> >  imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve
> >  imapsieve_mailbox1_causes = COPY
> >  imapsieve_mailbox1_name = Spam
> >  imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve
> >  imapsieve_mailbox2_causes = COPY
> >  imapsieve_mailbox2_from = Spam
> >  imapsieve_mailbox2_name = *
> >  quota = maildir:User quota
> >  quota_exceeded_message = User %u has exhausted allowed storage space.
> >  sieve = 
> > file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve
> >  sieve_before = /var/vmail/sieve/global/spam-global.sieve
> >  sieve_global_extensions = +vnd.dovecot.pipe
> >  sieve_pipe_bin_dir = /usr/bin
> >  sieve_plugins = sieve_imapsieve sieve_extprograms
> > }
> > protocols = imap lmtp sieve
> > service auth {
> >  unix_listener /var/spool/postfix/private/auth {
> >  group = postfix
> >  mode = 0660
> >  user = postfix
> >  }
> >  unix_listener auth-userdb {
> >  group = vmail
> >  mode = 0660
> >  user = vmail
> >  }
> > }
> > service imap-login {
> >  inet_listener imap {
> >  port = 143
> >  }
> >  process_min_avail = 1
> >  service_count = 1
> > }
> > service lmtp {
> >  unix_listener /var/spool/postfix/private/dovecot-lmtp {
> >  group = postfix
> >  mode = 0660
> >  user = postfix
> >  }
> >  user = vmail
> > }
> > service managesieve-login {
> >  inet_listener sieve {
> >  port = 4190
> >  }
> > }
> > ssl = required
> > ssl_ca =  > ssl_cert =  > ssl_cipher_list = 
> > ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
> > ssl_dh = # hidden, use -P to show it
> > ssl_key = # hidden, use -P to show it
> > ssl_min_protocol = TLSv1.2
> > userdb {
> >  args = /etc/dovecot/dovecot-sql.conf
> >  driver = sql
> > 

Re: Migration dovecot server with local users to dovecot with virtual mailboxes

[t Seeger]

Thank you for the link, unfortunately I am missing the crucial clue. I get
the directories backed up, but I don't get them imported properly all
mails are displayed as unseen. i tried with simple pasting and the doveadm
import command. Is there a trick to preserve the flags? Maybe it is because
the old dovecot server uses short username without the @ and the domain
name and the new one uses the mail address to identify the user.

On Thu, Jun 8, 2023 at 3:26 PM aki.tuomi via dovecot 
wrote:

> Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/
>
> Aki
>
>  Original message 
> From: tseeger...@gmail.com
> Date: 6/8/23 16:10 (GMT+02:00)
> To: dovecot@dovecot.org
> Subject: Migration dovecot server with local users to dovecot with virtual
> mailboxes
>
> Hello,
> we are using a dovecot server with NIS, we want to transfer it to a new
> setup. As backend a mysql server will be used in the future.
> My problem is, if I just copy the maildir or use "doveadm import" all
> mails are flagged as "unseen". How can i preserve the flags?
>
> This is how I have tried it so far.
> root@mail / $ doveadm import -s -u testuser@testdomain.local
> maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"
>
> As a "workaround" I tried to change the flags.
> root@mail / $ doveadm -v flags add -u testuser@testdomain.local "Seen"
> "ALL"
> This led partially to the desired success, the mails are shown as "seen",
> but the folders (e.g. Roundcube) still show unread mails.
>
> dovecot -n
> 
> # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.13 (cdd19fe3)
> # OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7
> # Hostname: mail.testdomain.local
> auth_mechanisms = plain login
> mail_fsync = always
> mail_gid = vmail
> mail_home = /var/vmail/mailboxes/%d/%n
> mail_location = maildir:~/mail:LAYOUT=fs:INDEX=MEMORY
> mail_privileged_group = vmail
> mail_uid = vmail
> managesieve_notify_capability = mailto
> managesieve_sieve_capability = fileinto reject envelope encoded-character
> vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
> copy include variables body enotify environment mailbox date index ihave
> duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve
> mmap_disable = yes
> namespace inbox {
>   inbox = yes
>   location =
>   mailbox Drafts {
> auto = subscribe
> special_use = \Drafts
>   }
>   mailbox Sent {
> auto = subscribe
> special_use = \Sent
>   }
>   mailbox Spam {
> auto = subscribe
> special_use = \Junk
>   }
>   mailbox Trash {
> auto = subscribe
> special_use = \Trash
>   }
>   prefix =
> }
> passdb {
>   args = /etc/dovecot/dovecot-sql.conf
>   driver = sql
> }
> plugin {
>   imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve
>   imapsieve_mailbox1_causes = COPY
>   imapsieve_mailbox1_name = Spam
>   imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve
>   imapsieve_mailbox2_causes = COPY
>   imapsieve_mailbox2_from = Spam
>   imapsieve_mailbox2_name = *
>   quota = maildir:User quota
>   quota_exceeded_message = User %u has exhausted allowed storage space.
>   sieve =
> file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve
>   sieve_before = /var/vmail/sieve/global/spam-global.sieve
>   sieve_global_extensions = +vnd.dovecot.pipe
>   sieve_pipe_bin_dir = /usr/bin
>   sieve_plugins = sieve_imapsieve sieve_extprograms
> }
> protocols = imap lmtp sieve
> service auth {
>   unix_listener /var/spool/postfix/private/auth {
> group = postfix
> mode = 0660
> user = postfix
>   }
>   unix_listener auth-userdb {
> group = vmail
> mode = 0660
> user = vmail
>   }
> }
> service imap-login {
>   inet_listener imap {
> port = 143
>   }
>   process_min_avail = 1
>   service_count = 1
> }
> service lmtp {
>   unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0660
> user = postfix
>   }
>   user = vmail
> }
> service managesieve-login {
>   inet_listener sieve {
> port = 4190
>   }
> }
> ssl = required
> ssl_ca =  ssl_cert =  ssl_cipher_list =
> ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
> ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -P to show it
> ssl_min_protocol = TLSv1.2
> userdb {
>   args = /etc/dovecot/dovecot-sql.conf
>   driver = sql
> }
> protocol imap {
>   imap_idle_notify_interval = 29 mins
>   mail_max_userip_connections = 20
>   mail_plugins = " quota imap_quota imap_sieve"
> }
> protocol lmtp {
>   mail_plugins = " sieve notify push_notification quota"
>   postmaster_address = postmaster@testdomain.local
> }
> 
>
> Thanks for your help

RE: Migration dovecot server with local users to dovecot with virtual mailboxes

[aki.tuomi via dovecot]

Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/Aki
 Original message From: tseeger...@gmail.com Date: 6/8/23  
16:10  (GMT+02:00) To: dovecot@dovecot.org Subject: Migration dovecot server 
with local users to dovecot with virtual
mailboxes Hello, we are using a dovecot server with NIS, we want to 
transfer it to a new setup. As backend a mysql server will be used in the 
future. My problem is, if I just copy the maildir or use "doveadm import" all 
mails are flagged as "unseen". How can i preserve the flags?This is how I have 
tried it so far.root@mail / $ doveadm import -s -u testuser@testdomain.local 
maildir:/tmp/testuser-maildir-230608/Maildir/:INDEX=MEMORY "" "All"As a 
"workaround" I tried to change the flags.root@mail / $ doveadm -v flags add -u 
testuser@testdomain.local "Seen" "ALL"This led partially to the desired 
success, the mails are shown as "seen", but the folders (e.g. Roundcube) still 
show unread mails.dovecot -n# 
2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf# Pigeonhole version 0.5.13 
(cdd19fe3)# OS: Linux 5.10.0-23-cloud-amd64 x86_64 Debian 11.7 # Hostname: 
mail.testdomain.localauth_mechanisms = plain loginmail_fsync = alwaysmail_gid = 
vmailmail_home = /var/vmail/mailboxes/%d/%nmail_location = 
maildir:~/mail:LAYOUT=fs:INDEX=MEMORYmail_privileged_group = vmailmail_uid = 
vmailmanagesieve_notify_capability = mailtomanagesieve_sieve_capability = 
fileinto reject envelope encoded-character vacation subaddress 
comparator-i;ascii-numeric relational regex imap4flags copy include variables 
body enotify environment mailbox date index ihave duplicate mime foreverypart 
extracttext imapsieve vnd.dovecot.imapsievemmap_disable = yesnamespace inbox {  
inbox = yes  location =   mailbox Drafts {    auto = subscribe    special_use = 
\Drafts  }  mailbox Sent {    auto = subscribe    special_use = \Sent  }  
mailbox Spam {    auto = subscribe    special_use = \Junk  }  mailbox Trash {   
 auto = subscribe    special_use = \Trash  }  prefix = }passdb {  args = 
/etc/dovecot/dovecot-sql.conf  driver = sql}plugin {  imapsieve_mailbox1_before 
= file:/var/vmail/sieve/global/learn-spam.sieve  imapsieve_mailbox1_causes = 
COPY  imapsieve_mailbox1_name = Spam  imapsieve_mailbox2_before = 
file:/var/vmail/sieve/global/learn-ham.sieve  imapsieve_mailbox2_causes = COPY  
imapsieve_mailbox2_from = Spam  imapsieve_mailbox2_name = *  quota = 
maildir:User quota  quota_exceeded_message = User %u has exhausted allowed 
storage space.  sieve = 
file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve
  sieve_before = /var/vmail/sieve/global/spam-global.sieve  
sieve_global_extensions = +vnd.dovecot.pipe  sieve_pipe_bin_dir = /usr/bin  
sieve_plugins = sieve_imapsieve sieve_extprograms}protocols = imap lmtp 
sieveservice auth {  unix_listener /var/spool/postfix/private/auth {    group = 
postfix    mode = 0660    user = postfix  }  unix_listener auth-userdb {    
group = vmail    mode = 0660    user = vmail  }}service imap-login {  
inet_listener imap {    port = 143  }  process_min_avail = 1  service_count = 
1}service lmtp {  unix_listener /var/spool/postfix/private/dovecot-lmtp {    
group = postfix    mode = 0660    user = postfix  }  user = vmail}service 
managesieve-login {  inet_listener sieve {    port = 4190  }}ssl = 
requiredssl_ca = 
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Thomas Winterstein]

When doing migration, it is very useful to construct a temporary 
dovecot-migration.conf which lacks *any* automatic mailbox creation and has 
only the bare minimum you need (sieve needs to be configured, and mailbox 
attributes). This means no autocreate/autosubscribe loaded, and no auto=create 
or auto=subscribe in namespace config. It is recommended not to have any 
mailbox Name entries in your namespace config.

You should use doveadm -c /path/to/dovecot-migration.conf backup command on 
initial sync.

The mailboxes must not exist before you do initial sync, if they do, you run 
into troubles.


I tried what you said, no autocreate/autosubscribe... etc., but none of 
my tests with minimal migration config changed anything in the GUID 
behavior.


No folders for the users existed before this command.

doveadm -D -v -c minimal-conf backup -R -u USER imapc: > output 2>&1


doveadm(USER): Debug: Effective uid=500, gid=500, home=/srv/mail/v/USER
doveadm(USER): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, 
hidden=no, list=yes, subscriptions=yes location=mdbox:/srv/mail/v/USER
doveadm(USER): Debug: fs: root=/srv/mail/v/USER, index=, indexpvt=, control=, 
inbox=, alt=
doveadm(USER): Debug: Namespace : Using permissions from /srv/mail/v/USER: 
mode=0700 gid=default
dsync(USER): Debug: Effective uid=500, gid=500, home=/srv/mail/v/USER
dsync(USER): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, 
hidden=no, list=yes, subscriptions=yes location=imapc:
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Created new 
connection
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Looking up IP 
address (reconnect_ok=true, last_connect=1610467047)
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Connecting to 
137.250.1.99:143
dsync(USER): Info: imapc(zitrone.rz.uni-augsburg.de:143): Connected to 
137.250.1.99:143 (local 137.250.1.121:41094)
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Server capabilities: 
IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN 
AUTH=LOGIN
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Authenticating as 
admin for user USER
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Server capabilities: 
IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY 
THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH LIST-STATUS QUOTA
dsync(USER): Debug: imapc(zitrone.rz.uni-augsburg.de:143): Authenticated 
successfully
dsync(USER): Debug: imapc: root=, index=, indexpvt=, control=, inbox=, alt=
dsync(USER): Debug: brain S: Local mailbox tree: Trash 
guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1598518510 uid_next=434 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain M: Remote mailbox tree: Trash 
guid=7f5af7ba291b2df1a11d573bdb55d7e9 uid_validity=1598518510 uid_next=434 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain S: Local mailbox tree: Sent 
guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1598518508 uid_next=220 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain M: Remote mailbox tree: Sent 
guid=bfb2e03fdce327671e82bf173b1ccb8b uid_validity=1598518508 uid_next=220 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain S: Local mailbox tree: Drafts 
guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1598518507 uid_next=10 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain M: Remote mailbox tree: Drafts 
guid=e0187b65e763143666d22094cedfe6a4 uid_validity=1598518507 uid_next=10 
subs=yes last_change=0 last_subs=0
dsync(USER): Debug: brain S: Local mailbox tree: INBOX 
guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1598518506 uid_next=1049 
subs=no last_change=0 last_subs=0
dsync(USER): Debug: brain M: Remote mailbox tree: INBOX 
guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1598518506 uid_next=1049 
subs=no last_change=0 last_subs=0

...


for user in USER; do echo $user ; for mailbox in `ls 
/srv/mail/v/$user/mailboxes/`; do echo $mailbox; doveadm search -u $user 
mailbox $mailbox ALL | head -n 1; done ; done

USER
Drafts
INBOX
c92f64f79f0d1ed01e6d5b314f04886c 28
Junk
Sent
bfb2e03fdce327671e82bf173b1ccb8b 1
Trash
7f5af7ba291b2df1a11d573bdb55d7e9 1



doveadm -D -v -c minimal-conf backup -R -u USER2 imapc: > output 2>&1


doveadm(USER2): Debug: Effective uid=500, gid=500, home=/srv/mail/v/USER2
doveadm(USER2): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, 
hidden=no, list=yes, subscriptions=yes location=mdbox:/srv/mail/v/USER2
doveadm(USER2): Debug: fs: root=/srv/mail/v/USER2, index=, indexpvt=, control=, 
inbox=, alt=
doveadm(USER2): Debug: Namespace : Using permissions from /srv/mail/v/USER2: 
mode=0700 gid=default
dsync(USER2): Debug: Effective uid=500, gid=500, home=/srv/mail/v/USER2
dsync(USER2): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, 

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Aki Tuomi]

> On 11/01/2021 05:18 Thomas Winterstein 
>  wrote:
> 
>  
> we were able to narrow down the cause of the problem.
> 
> 
> After the initial dsync migration process the mailbox GUIDs are the same 
> for each mailbox-name across all users.
>   Is this intended behaviour of dsync?
>   If not, how can this be changed?
> 
> 
> After the first replication process the Inboxes of ~20% of users get 
> different mailbox GUIDs.
> 
> 
> During the next incremental dsync process the mailbox GUIDs of these 
> ~20% get overridden by the inital one.
> 
> 
> Then the incremental replication duplicates those Inboxes where the 
> mailbox GUIDs don't match.
> 
> 
> Any ideas?
> 
> 
> thanks
> Thomas
> 
> On 07.01.2021 16:41, Thomas Winterstein wrote:
> >>> dsync is intended to be used to change mailbox format, so it should 
> >>> work just fine.
> > 
> > that's exactly what we thought and why we use dsync to migrate like 
> > described here
> > 
> >    https://wiki2.dovecot.org/Migration/Dsync
> > 
> > 
> > Our replication is configured according to
> > 
> >    https://wiki.dovecot.org/Replication
> > 
> > 
> > Both processes run separately in time.
> > 
> > 
> > Still on some accounts mails of Inbox or another folder get duplicated. 
> > We're currently trying to debug this.
> > 
> > what are we missing?
> > 
> > thanks
> > Thomas
> > 
> > On 07.01.2021 10:21, Aki Tuomi wrote:
> >> dsync is intended to be used to change mailbox format, so it should 
> >> work just fine.
> >>
> >> Aki
> >>
> >>> On 07/01/2021 11:17 Andrea Gabellini 
> >>>  wrote:
> >>>
> >>> Hello,
> >>>
> >>> I had a similar problem some time ago, and the problem was the mailbox
> >>> format change.
> >>>
> >>> Please try to migrate with the same format.
> >>>
> >>> Andrea
> >>>
> >>> Il 05/01/21 15:02, Thomas Winterstein ha scritto:
>  No one?
> 
>  If there are limitations in regards to how dsync in migration and
>  replication can operate together these should be stated clearly in the
>  documentation.
> 
>  On 23.12.2020 20:33, Thomas Winterstein wrote:
> > Hello everyone,
> >
> >
> > we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
> > (mdbox). The new cluster has two backend mail servers which replicate
> > through doveadm replicator. To move the data initially we use doveadm
> > backup (imapc).
> >
> > arb
> > Our migration command
> >    doveadm -o mail_fsync=never backup -R -u $user imapc:
> >
> >
> > To test the replication of new and purge of old mails with live data
> > changes we ran imapc on a daily basis but encountered the problem
> > that some mailboxes multiplied in size. We then made sure that imapc
> > and replication don't run at the same time but after the first
> > incremental imapc process, we still had the same problems.
> >
> >
> > The doveadm-backup man-page states that it's possible to run it
> > multiple times during migration. But is it also possible to have the
> > replicator running in between? From our understanding the doveadm
> > backup should just work as an imap connection between the servers,
> > synchronizing all changes made on the source to the destination. Or
> > does the conversion from maildir to mdbox format in our case produce
> > the problems?
> >
> >
> > If you're not supposed to run the replicator before having fully
> > migrated, how can we shorten the downtime? rsync? And how can we be
> > sure that similar problems don't occur after the migration if we
> > can't test all mechanisms together with live data?
> >
> >
> > thanks
> 
> 
> >>>


When doing migration, it is very useful to construct a temporary 
dovecot-migration.conf which lacks *any* automatic mailbox creation and has 
only the bare minimum you need (sieve needs to be configured, and mailbox 
attributes). This means no autocreate/autosubscribe loaded, and no auto=create 
or auto=subscribe in namespace config. It is recommended not to have any 
mailbox Name entries in your namespace config.

You should use doveadm -c /path/to/dovecot-migration.conf backup command on 
initial sync. 

The mailboxes must not exist before you do initial sync, if they do, you run 
into troubles.

Aki

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Thomas Winterstein]

we were able to narrow down the cause of the problem.


After the initial dsync migration process the mailbox GUIDs are the same 
for each mailbox-name across all users.

Is this intended behaviour of dsync?
If not, how can this be changed?


After the first replication process the Inboxes of ~20% of users get 
different mailbox GUIDs.



During the next incremental dsync process the mailbox GUIDs of these 
~20% get overridden by the inital one.



Then the incremental replication duplicates those Inboxes where the 
mailbox GUIDs don't match.



Any ideas?


thanks
Thomas

On 07.01.2021 16:41, Thomas Winterstein wrote:
dsync is intended to be used to change mailbox format, so it should 
work just fine.


that's exactly what we thought and why we use dsync to migrate like 
described here


   https://wiki2.dovecot.org/Migration/Dsync


Our replication is configured according to

   https://wiki.dovecot.org/Replication


Both processes run separately in time.


Still on some accounts mails of Inbox or another folder get duplicated. 
We're currently trying to debug this.


what are we missing?

thanks
Thomas

On 07.01.2021 10:21, Aki Tuomi wrote:
dsync is intended to be used to change mailbox format, so it should 
work just fine.


Aki

On 07/01/2021 11:17 Andrea Gabellini 
 wrote:


Hello,

I had a similar problem some time ago, and the problem was the mailbox
format change.

Please try to migrate with the same format.

Andrea

Il 05/01/21 15:02, Thomas Winterstein ha scritto:

No one?

If there are limitations in regards to how dsync in migration and
replication can operate together these should be stated clearly in the
documentation.

On 23.12.2020 20:33, Thomas Winterstein wrote:

Hello everyone,


we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
(mdbox). The new cluster has two backend mail servers which replicate
through doveadm replicator. To move the data initially we use doveadm
backup (imapc).

arb
Our migration command
   doveadm -o mail_fsync=never backup -R -u $user imapc:


To test the replication of new and purge of old mails with live data
changes we ran imapc on a daily basis but encountered the problem
that some mailboxes multiplied in size. We then made sure that imapc
and replication don't run at the same time but after the first
incremental imapc process, we still had the same problems.


The doveadm-backup man-page states that it's possible to run it
multiple times during migration. But is it also possible to have the
replicator running in between? From our understanding the doveadm
backup should just work as an imap connection between the servers,
synchronizing all changes made on the source to the destination. Or
does the conversion from maildir to mdbox format in our case produce
the problems?


If you're not supposed to run the replicator before having fully
migrated, how can we shorten the downtime? rsync? And how can we be
sure that similar problems don't occur after the migration if we
can't test all mechanisms together with live data?


thanks





--
__
Daddy, why doesn't this magnet pick up this floppy ?
__

TIM San Marino S.p.A.
Andrea Gabellini
Engineering R
TIM San Marino S.p.A. - https://www.telecomitalia.sm
Via Ventotto Luglio, 212 - Piano -2
47893 - Borgo Maggiore - Republic of San Marino
Tel: (+378) 0549 886237
Fax: (+378) 0549 886188


--
Informativa Privacy

Questa email ha per destinatari dei contatti presenti negli archivi 
di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e 
tutelate nel rispetto della normativa vigente sulla protezione dei 
dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o 
variazioni e/o la cancellazione dei vostri dati presenti nei nostri 
archivi potete inviare una email a priv...@telecomitalia.sm.


Avviso di Riservatezza

Il contenuto di questa e-mail e degli eventuali allegati e' 
strettamente confidenziale e destinato alla/e persona/e a cui e' 
indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo 
di segnalarcelo immediatamente e di cancellarla dal vostro computer. 
E' fatto divieto di copiare e divulgare il contenuto di questa 
e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da 
parte di persone terze o comunque non indicate nella presente e-mail 
potra' essere perseguito ai sensi di legge.






--
Thomas Winterstein  http://www.rz.uni-augsburg.de/
Universität Augsburg, Rechenzentrum . Tel. (0821) 598-2068
86135 Augsburg .. Fax. (0821) 598-2028

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Thomas Winterstein]

dsync is intended to be used to change mailbox format, so it should work just 
fine.


that's exactly what we thought and why we use dsync to migrate like 
described here


  https://wiki2.dovecot.org/Migration/Dsync


Our replication is configured according to

  https://wiki.dovecot.org/Replication


Both processes run separately in time.


Still on some accounts mails of Inbox or another folder get duplicated. 
We're currently trying to debug this.


what are we missing?

thanks
Thomas

On 07.01.2021 10:21, Aki Tuomi wrote:

dsync is intended to be used to change mailbox format, so it should work just 
fine.

Aki


On 07/01/2021 11:17 Andrea Gabellini  wrote:

  
Hello,


I had a similar problem some time ago, and the problem was the mailbox
format change.

Please try to migrate with the same format.

Andrea

Il 05/01/21 15:02, Thomas Winterstein ha scritto:

No one?

If there are limitations in regards to how dsync in migration and
replication can operate together these should be stated clearly in the
documentation.

On 23.12.2020 20:33, Thomas Winterstein wrote:

Hello everyone,


we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
(mdbox). The new cluster has two backend mail servers which replicate
through doveadm replicator. To move the data initially we use doveadm
backup (imapc).

arb
Our migration command
   doveadm -o mail_fsync=never backup -R -u $user imapc:


To test the replication of new and purge of old mails with live data
changes we ran imapc on a daily basis but encountered the problem
that some mailboxes multiplied in size. We then made sure that imapc
and replication don't run at the same time but after the first
incremental imapc process, we still had the same problems.


The doveadm-backup man-page states that it's possible to run it
multiple times during migration. But is it also possible to have the
replicator running in between? From our understanding the doveadm
backup should just work as an imap connection between the servers,
synchronizing all changes made on the source to the destination. Or
does the conversion from maildir to mdbox format in our case produce
the problems?


If you're not supposed to run the replicator before having fully
migrated, how can we shorten the downtime? rsync? And how can we be
sure that similar problems don't occur after the migration if we
can't test all mechanisms together with live data?


thanks





--
__
Daddy, why doesn't this magnet pick up this floppy ?
__

TIM San Marino S.p.A.
Andrea Gabellini
Engineering R
TIM San Marino S.p.A. - https://www.telecomitalia.sm
Via Ventotto Luglio, 212 - Piano -2
47893 - Borgo Maggiore - Republic of San Marino
Tel: (+378) 0549 886237
Fax: (+378) 0549 886188


--
Informativa Privacy

Questa email ha per destinatari dei contatti presenti negli archivi di TIM San 
Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto 
della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). 
Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati 
presenti nei nostri archivi potete inviare una email a priv...@telecomitalia.sm.

Avviso di Riservatezza

Il contenuto di questa e-mail e degli eventuali allegati e' strettamente 
confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete 
ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente 
e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare 
il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui 
contenute da parte di persone terze o comunque non indicate nella presente 
e-mail potra' essere perseguito ai sensi di legge.



--
Thomas Winterstein  http://www.rz.uni-augsburg.de/
Universität Augsburg, Rechenzentrum . Tel. (0821) 598-2068
86135 Augsburg .. Fax. (0821) 598-2028

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Aki Tuomi]

dsync is intended to be used to change mailbox format, so it should work just 
fine.

Aki

> On 07/01/2021 11:17 Andrea Gabellini  
> wrote:
> 
>  
> Hello,
> 
> I had a similar problem some time ago, and the problem was the mailbox
> format change.
> 
> Please try to migrate with the same format.
> 
> Andrea
> 
> Il 05/01/21 15:02, Thomas Winterstein ha scritto:
> > No one?
> >
> > If there are limitations in regards to how dsync in migration and
> > replication can operate together these should be stated clearly in the
> > documentation.
> >
> > On 23.12.2020 20:33, Thomas Winterstein wrote:
> >> Hello everyone,
> >>
> >>
> >> we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
> >> (mdbox). The new cluster has two backend mail servers which replicate
> >> through doveadm replicator. To move the data initially we use doveadm
> >> backup (imapc).
> >>
> >> arb
> >> Our migration command
> >>   doveadm -o mail_fsync=never backup -R -u $user imapc:
> >>
> >>
> >> To test the replication of new and purge of old mails with live data
> >> changes we ran imapc on a daily basis but encountered the problem
> >> that some mailboxes multiplied in size. We then made sure that imapc
> >> and replication don't run at the same time but after the first
> >> incremental imapc process, we still had the same problems.
> >>
> >>
> >> The doveadm-backup man-page states that it's possible to run it
> >> multiple times during migration. But is it also possible to have the
> >> replicator running in between? From our understanding the doveadm
> >> backup should just work as an imap connection between the servers,
> >> synchronizing all changes made on the source to the destination. Or
> >> does the conversion from maildir to mdbox format in our case produce
> >> the problems?
> >>
> >>
> >> If you're not supposed to run the replicator before having fully
> >> migrated, how can we shorten the downtime? rsync? And how can we be
> >> sure that similar problems don't occur after the migration if we
> >> can't test all mechanisms together with live data?
> >>
> >>
> >> thanks
> >
> >
> 
> -- 
> __
> Daddy, why doesn't this magnet pick up this floppy ?
> __
> 
> TIM San Marino S.p.A.
> Andrea Gabellini
> Engineering R
> TIM San Marino S.p.A. - https://www.telecomitalia.sm
> Via Ventotto Luglio, 212 - Piano -2
> 47893 - Borgo Maggiore - Republic of San Marino
> Tel: (+378) 0549 886237
> Fax: (+378) 0549 886188
> 
> 
> --
> Informativa Privacy
> 
> Questa email ha per destinatari dei contatti presenti negli archivi di TIM 
> San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel 
> rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 
> 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione 
> dei vostri dati presenti nei nostri archivi potete inviare una email a 
> priv...@telecomitalia.sm.
> 
> Avviso di Riservatezza
> 
> Il contenuto di questa e-mail e degli eventuali allegati e' strettamente 
> confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete 
> ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo 
> immediatamente e di cancellarla dal vostro computer. E' fatto divieto di 
> copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo 
> delle informazioni qui contenute da parte di persone terze o comunque non 
> indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Andrea Gabellini]

Hello,

I had a similar problem some time ago, and the problem was the mailbox
format change.

Please try to migrate with the same format.

Andrea

Il 05/01/21 15:02, Thomas Winterstein ha scritto:
> No one?
>
> If there are limitations in regards to how dsync in migration and
> replication can operate together these should be stated clearly in the
> documentation.
>
> On 23.12.2020 20:33, Thomas Winterstein wrote:
>> Hello everyone,
>>
>>
>> we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
>> (mdbox). The new cluster has two backend mail servers which replicate
>> through doveadm replicator. To move the data initially we use doveadm
>> backup (imapc).
>>
>> arb
>> Our migration command
>>   doveadm -o mail_fsync=never backup -R -u $user imapc:
>>
>>
>> To test the replication of new and purge of old mails with live data
>> changes we ran imapc on a daily basis but encountered the problem
>> that some mailboxes multiplied in size. We then made sure that imapc
>> and replication don't run at the same time but after the first
>> incremental imapc process, we still had the same problems.
>>
>>
>> The doveadm-backup man-page states that it's possible to run it
>> multiple times during migration. But is it also possible to have the
>> replicator running in between? From our understanding the doveadm
>> backup should just work as an imap connection between the servers,
>> synchronizing all changes made on the source to the destination. Or
>> does the conversion from maildir to mdbox format in our case produce
>> the problems?
>>
>>
>> If you're not supposed to run the replicator before having fully
>> migrated, how can we shorten the downtime? rsync? And how can we be
>> sure that similar problems don't occur after the migration if we
>> can't test all mechanisms together with live data?
>>
>>
>> thanks
>
>

-- 
__
Daddy, why doesn't this magnet pick up this floppy ?
__

TIM San Marino S.p.A.
Andrea Gabellini
Engineering R
TIM San Marino S.p.A. - https://www.telecomitalia.sm
Via Ventotto Luglio, 212 - Piano -2
47893 - Borgo Maggiore - Republic of San Marino
Tel: (+378) 0549 886237
Fax: (+378) 0549 886188


--
Informativa Privacy

Questa email ha per destinatari dei contatti presenti negli archivi di TIM San 
Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto 
della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). 
Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati 
presenti nei nostri archivi potete inviare una email a priv...@telecomitalia.sm.

Avviso di Riservatezza

Il contenuto di questa e-mail e degli eventuali allegati e' strettamente 
confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete 
ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente 
e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare 
il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui 
contenute da parte di persone terze o comunque non indicate nella presente 
e-mail potra' essere perseguito ai sensi di legge.

Re: migration with doveadm backup to new cluster running dovecot 2.2.36 and replicator

[Thomas Winterstein]

No one?

If there are limitations in regards to how dsync in migration and 
replication can operate together these should be stated clearly in the 
documentation.


On 23.12.2020 20:33, Thomas Winterstein wrote:

Hello everyone,


we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36 
(mdbox). The new cluster has two backend mail servers which replicate 
through doveadm replicator. To move the data initially we use doveadm 
backup (imapc).


arb
Our migration command
  doveadm -o mail_fsync=never backup -R -u $user imapc:


To test the replication of new and purge of old mails with live data 
changes we ran imapc on a daily basis but encountered the problem that 
some mailboxes multiplied in size. We then made sure that imapc and 
replication don't run at the same time but after the first incremental 
imapc process, we still had the same problems.



The doveadm-backup man-page states that it's possible to run it multiple 
times during migration. But is it also possible to have the replicator 
running in between? From our understanding the doveadm backup should 
just work as an imap connection between the servers, synchronizing all 
changes made on the source to the destination. Or does the conversion 
from maildir to mdbox format in our case produce the problems?



If you're not supposed to run the replicator before having fully 
migrated, how can we shorten the downtime? rsync? And how can we be sure 
that similar problems don't occur after the migration if we can't test 
all mechanisms together with live data?



thanks



--
Thomas Winterstein

Re: migration from 2.0.16

[Toni Mueller]

Hi,

On Thu, Dec 17, 2020 at 03:56:45PM +0100, Barbara M. wrote:
> Debian 10 is EOL on 2022

this may be true, but (1) you can probably expect Debian to have LTS for
this - they had for the last few distributions, extending their
livetimes to more than 5 years at least (I think Jessie was pulled
recently), and upgrades are usually smooth.

> Ubuntu LTS seems a solution, but I hadn't ever used it (I may be wrong, but
> in the past Canonical don't inspire me to much trust).

Me too. IMHO, Debian is the better choice, due to better QA and more
effort in backwards compatibility and upgradability. Also, Debian is
less driven by commercial considerations, and at least not directly
dependend on company policies.



A happy new year all around!


Enjoy,
Toni

RE: migration from 2.0.16

[Aki Tuomi]

> On 17/12/2020 15:38 Barbara M.  wrote:
> 
>  
> On Thu, 17 Dec 2020, Aki Tuomi wrote:
> 
> > I would recommend using dsync migration to get rid of mbox format. We no 
> > longer develop that format, and bugs are limited to reading mbox format.
> 
> Ok, but I assume that dovecot 2.3.x still support mbox?  (just in case the 
> mbox --> MailDir migration give more problems than expected expecially 
> with POP3 UIDL)
> 

It's not removed, but we don't focus on maintaining full functionality on it.

Please look at the wiki link on how to use pop3_migration_plugin to avoid UIDL 
problems.

> > I would also recommend using master password / master user login with 
> > doveadm sync, and do the synchronization over imapc: to get the data safely 
> > migrated to your new system.
> >
> > You should use
> >
> > doveadm sync -u user backup -R imapc:
> >
> > on the new server to pull the data from old server. See 
> > https://wiki.dovecot.org/Migration/Dsync for more details.
> 
> Ok, but My old server is 2.0.16.
> The suggested URL say:  "You need Dovecot v2.1.4+ for this."
> I can't understand if it refers to source or destination server
> 
> I tried to activate master password / master user, but I get:
> 
> # telnet 0 143
> Trying 0.0.0.0...
> Connected to 0.
> Escape character is '^]'.
> * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE 
> STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
> a login USER*MASTER MASTERPWD
> a NO [AUTHENTICATIONFAILED] Authentication failed.
> 
> Nothing in dovecot.[log|info.log]
> 
> (real user/pwd replaced)
> /etc/dovecot/passwd.masterusers created using htpasswd  ... 
> tried with standard pwd created by htpasswd or replacing the encrypted 
> pwd with a know passwd form /etc/shadow.
> 
> My current dovecot -n :
> 

Try enabling auth_debug=yes

You need to move master passdb before pam. And you need 
auth_master_user_separator=*

Aki

> # 2.0.16: /etc/dovecot/dovecot.conf
> # OS: Linux 2.6.32-48-pve x86_64 CentOS release 6.10 (Final)
> auth_mechanisms = plain login
> default_client_limit = 3000
> default_process_limit = 500
> disable_plaintext_auth = no
> info_log_path = /var/log/mail/dovecot.info.log
> log_path = /var/log/mail/dovecot.log
> mail_full_filesystem_access = yes
> mail_location = mbox:~/:INBOX=/var/mail/%u
> mbox_read_locks = dotlock fcntl
> passdb {
>driver = pam
> }
> passdb {
>args = /etc/dovecot/passwd.masterusers
>driver = passwd-file
>master = yes
>pass = yes
> }
> protocols = imap pop3
> service imap {
>process_limit = 512
> }
> service pop3 {
>process_limit = 1024
> }
> ssl_cert =  ssl_cipher_list = 
> ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:RC4:HIGH:MEDIUM:+TLSv1:+TLSv1.1:+TLSv1.2:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!AESGCM
> ssl_key =  userdb {
>driver = passwd
> }
> protocol imap {
>imap_id_log = *
> }
> protocol pop3 {
>pop3_uidl_format = %08Xu%08Xv
> }
> 
> 
> 
> Thanks, B.

Re: migration from 2.0.16

[infoomatic]

On 17.12.20 15:56, Barbara M. wrote:
>
> We own the servers and use CT (LXC).
> The IBM move is clear, but going to C7 today seems to me not a good
> choice. It is in its descending stage and in a couple of years
> packages are going to became very outdated.
> If RH8 remain "open source" I suppose the community or some interested
> medium level company that use CentOS for their business can became a
> new CentOS and switch to a different named distro is supposed to be
> only a question of replace repositories.
> That seems to me a smoother path (IMHO).
> Debian 10 is EOL on 2022
> Ubuntu LTS seems a solution, but I hadn't ever used it (I may be
> wrong, but in the past Canonical don't inspire me to much trust).
>
Maybe Rocky Linux will become a drop-in replacement for CentOS, see
https://rockylinux.org/ - it is led by the founder of CentOS and was
initated after the recent news concerning CentOS.


If it does not have to be Linux I'll throw in FreeBSD + jails (= system
level containers) as a recommendation. After quite some problems with
major upgrades on Ubuntu I moved some of the servers to FreeBSD and now
I am happy. (Going from one Debian stable to the next Debian stable also
turned out to work much better than going from one Ubuntu LTS to the
next Ubuntu LTS version ... but that is just my personal experience on <
50 servers)

Re: migration from 2.0.16

[lists]

I have found opensuse to be very stable and the upgrades to be drama free IF 
(big if) you stick to the distribution repositories. For a server, sticking to 
the disty repos is very likely. It is desktop users (me) that load a lot of 
software from other repos that occasionally muck things up.

I run centos 7 on my servers and opensuse on the desktop. They are very 
similar. I always have trouble when I have to use Debian, which these days is 
only on a R Pi. Opensuse can use three different package managers, one of which 
being yum. 






  Original Message  


From: barb...@rfx.it
Sent: December 17, 2020 6:57 AM
To: dovecot@dovecot.org
Subject: RE: migration from 2.0.16


On Thu, 17 Dec 2020, Marc Roos wrote:

> I would not choose centos 8 it has EOL < than centos7. IBM is pulling
> the plug on the centos distribution, and makes it more or less a beta
> for the rhel. Thus centos7 and then you have a few years to decide what
> to choose. Enough to go to full containerized eg. ;)

We own the servers and use CT (LXC).
The IBM move is clear, but going to C7 today seems to me not a good
choice.
It is in its descending stage and in a couple of years packages are going
to became very outdated.
If RH8 remain "open source" I suppose the community or some interested
medium level company that use CentOS for their business can became a new
CentOS and switch to a different named distro is supposed to be only a
question of replace repositories.
That seems to me a smoother path (IMHO).
Debian 10 is EOL on 2022
Ubuntu LTS seems a solution, but I hadn't ever used it (I may be wrong,
but in the past Canonical don't inspire me to much trust).

Other options (not too "exotic")?


> You do not need to rsync, dovecot can sync messages. I am just in the
> process of migrating a server from a different network to a different
> mailbox format.
>
> My approach was to create an 'archive' namespace on shared slower but
> distributed storage so I do not have to move to much data.

I am studying the situation, but there are many variables and the old age
of the source server probably meke it more complex.
And I am not a dovecot expert ...

Thanks, B.

RE: migration from 2.0.16

[Barbara M.]

On Thu, 17 Dec 2020, Marc Roos wrote:


I would not choose centos 8 it has EOL < than centos7. IBM is pulling
the plug on the centos distribution, and makes it more or less a beta
for the rhel. Thus centos7 and then you have a few years to decide what
to choose. Enough to go to full containerized eg. ;)


We own the servers and use CT (LXC).
The IBM move is clear, but going to C7 today seems to me not a good 
choice. 
It is in its descending stage and in a couple of years packages are going 
to became very outdated.
If RH8 remain "open source" I suppose the community or some interested 
medium level company that use CentOS for their business can became a new 
CentOS and switch to a different named distro is supposed to be only a 
question of replace repositories.

That seems to me a smoother path (IMHO).
Debian 10 is EOL on 2022
Ubuntu LTS seems a solution, but I hadn't ever used it (I may be wrong, 
but in the past Canonical don't inspire me to much trust).


Other options (not too "exotic")?



You do not need to rsync, dovecot can sync messages. I am just in the
process of migrating a server from a different network to a different
mailbox format.

My approach was to create an 'archive' namespace on shared slower but
distributed storage so I do not have to move to much data.


I am studying the situation, but there are many variables and the old age 
of the source server probably meke it more complex.

And I am not a dovecot expert ...

Thanks, B.

RE: migration from 2.0.16

[Barbara M.]

On Thu, 17 Dec 2020, Aki Tuomi wrote:


I would recommend using dsync migration to get rid of mbox format. We no longer 
develop that format, and bugs are limited to reading mbox format.


Ok, but I assume that dovecot 2.3.x still support mbox?  (just in case the 
mbox --> MailDir migration give more problems than expected expecially 
with POP3 UIDL)



I would also recommend using master password / master user login with doveadm 
sync, and do the synchronization over imapc: to get the data safely migrated to 
your new system.

You should use

doveadm sync -u user backup -R imapc:

on the new server to pull the data from old server. See 
https://wiki.dovecot.org/Migration/Dsync for more details.


Ok, but My old server is 2.0.16.
The suggested URL say:  "You need Dovecot v2.1.4+ for this."
I can't understand if it refers to source or destination server

I tried to activate master password / master user, but I get:

# telnet 0 143
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE 
STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

a login USER*MASTER MASTERPWD
a NO [AUTHENTICATIONFAILED] Authentication failed.

Nothing in dovecot.[log|info.log]

(real user/pwd replaced)
/etc/dovecot/passwd.masterusers created using htpasswd  ... 
tried with standard pwd created by htpasswd or replacing the encrypted 
pwd with a know passwd form /etc/shadow.


My current dovecot -n :

# 2.0.16: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-48-pve x86_64 CentOS release 6.10 (Final)
auth_mechanisms = plain login
default_client_limit = 3000
default_process_limit = 500
disable_plaintext_auth = no
info_log_path = /var/log/mail/dovecot.info.log
log_path = /var/log/mail/dovecot.log
mail_full_filesystem_access = yes
mail_location = mbox:~/:INBOX=/var/mail/%u
mbox_read_locks = dotlock fcntl
passdb {
  driver = pam
}
passdb {
  args = /etc/dovecot/passwd.masterusers
  driver = passwd-file
  master = yes
  pass = yes
}
protocols = imap pop3
service imap {
  process_limit = 512
}
service pop3 {
  process_limit = 1024
}
ssl_cert = ssl_cipher_list = 
ECDHE-RSA-AES256-SHA384:AES256-SHA256:AES256-SHA256:RC4:HIGH:MEDIUM:+TLSv1:+TLSv1.1:+TLSv1.2:!MD5:!ADH:!aNULL:!eNULL:!NULL:!DH:!ADH:!EDH:!AESGCM

ssl_key = 

RE: migration from 2.0.16

[Marc Roos]

Oh interesting this imapc option. Is there any advantage of using that 
instead of what I am currently using 
 
doveadm  backup -n inbox -F /root/backup-rest-2.txt tcp:mail04.local:542

Also any difference between pulling or pushing the messages? To check, I 
have made some script that outputs messages of mailboxes that I can 
compare between source and destination server. But this of course does 
not show if messages are 100% ok.


[@ ~]# mailbox-ls.sh test size
listing mailboxes of test:
Archive messages=0
Archive/2011 messages=0
Archive/2012 messages=0
Archive/2013 messages=0
Archive/2014 messages=0
Archive/2015 messages=0
Archive/2016 messages=0
Archive/2017 messages=0
Archive/2018 messages=0
Archive/2019 messages=3500
Archive/Archive messages=1
Deleted Messages messages=28
Drafts messages=2
INBOX messages=1325
INBOX/test2 messages=3
Junk messages=2
Sent messages=1
Trash messages=132


-Original Message-
From: Aki Tuomi [mailto:aki.tu...@open-xchange.com] 
Sent: 17 December 2020 10:16
To: Marc Roos; barbara; dovecot
Subject: RE: migration from 2.0.16

I would recommend using dsync migration to get rid of mbox format. We no 
longer develop that format, and bugs are limited to reading mbox format.

I would also recommend using master password / master user login with 
doveadm sync, and do the synchronization over imapc: to get the data 
safely migrated to your new system.

You should use

doveadm sync -u user backup -R imapc:

on the new server to pull the data from old server. See 
https://wiki.dovecot.org/Migration/Dsync for more details.

Aki

> On 17/12/2020 11:08 Marc Roos  wrote:
> 
>  
> I would not choose centos 8 it has EOL < than centos7. IBM is pulling 
> the plug on the centos distribution, and makes it more or less a beta 
> for the rhel. Thus centos7 and then you have a few years to decide 
> what to choose. Enough to go to full containerized eg. ;)
> 
> You do not need to rsync, dovecot can sync messages. I am just in the 
> process of migrating a server from a different network to a different 
> mailbox format.
> 
> My approach was to create an 'archive' namespace on shared slower but 
> distributed storage so I do not have to move to much data.
> 
> 
> 
> -Original Message-
> From: Barbara M. [mailto:barb...@rfx.it]
> Sent: 17 December 2020 01:47
> To: dovecot@dovecot.org
> Subject: migration from 2.0.16
> 
> 
> I have an old server with CentOS 6.x and dovecot 2.0.16 (postfix-2.6.6 

> and roundcube), that was an update from a 1.x many years ago ...
> Users in /etc/passwd
> Mailbox format mbox
> some filtering via procmail
> About 5.000 users, 1 TB data (/var/mail + /home/users)
> 
> Obviously I am searching for a smooth upgrade path (with no or minimal 

> downtime and users problems) ;-)
> 
> Until few days ago my idea was a CentOS 8.x new box with the standard 
> default packages (dovecot-2.3.8, postfix-3.3, ...).
> Now this can be reconsidered. I suppose there will be a RockyLinux or 
> something equivalent but if there is a good reason I can consider 
> Debian or other OS if they have a decent EOL or some advantages.
> 
> Anyway, the more relevant problem at the moment is collect info for 
> the best approch to have a smooth dovecot upgrade.
> 
> My dream is the possibility to configure a new server and rsync the 
> data (/var/mail + /home/users), and, when the tests are satisfiable do 

> the final sync and swap the IP, but I suppose deleting the .imap 
> folders isn't a simple complete solution to compatibility problems.
> 
> Any hints, links, experiences are appreciated.
> 
> Thanks, B.

RE: migration from 2.0.16

[Aki Tuomi]

I would recommend using dsync migration to get rid of mbox format. We no longer 
develop that format, and bugs are limited to reading mbox format.

I would also recommend using master password / master user login with doveadm 
sync, and do the synchronization over imapc: to get the data safely migrated to 
your new system.

You should use

doveadm sync -u user backup -R imapc:

on the new server to pull the data from old server. See 
https://wiki.dovecot.org/Migration/Dsync for more details.

Aki

> On 17/12/2020 11:08 Marc Roos  wrote:
> 
>  
> I would not choose centos 8 it has EOL < than centos7. IBM is pulling 
> the plug on the centos distribution, and makes it more or less a beta 
> for the rhel. Thus centos7 and then you have a few years to decide what 
> to choose. Enough to go to full containerized eg. ;)
> 
> You do not need to rsync, dovecot can sync messages. I am just in the 
> process of migrating a server from a different network to a different 
> mailbox format. 
> 
> My approach was to create an 'archive' namespace on shared slower but 
> distributed storage so I do not have to move to much data.
> 
> 
> 
> -Original Message-
> From: Barbara M. [mailto:barb...@rfx.it] 
> Sent: 17 December 2020 01:47
> To: dovecot@dovecot.org
> Subject: migration from 2.0.16
> 
> 
> I have an old server with CentOS 6.x and dovecot 2.0.16 (postfix-2.6.6 
> and roundcube), that was an update from a 1.x many years ago ...
> Users in /etc/passwd
> Mailbox format mbox
> some filtering via procmail
> About 5.000 users, 1 TB data (/var/mail + /home/users)
> 
> Obviously I am searching for a smooth upgrade path (with no or minimal 
> downtime and users problems) ;-)
> 
> Until few days ago my idea was a CentOS 8.x new box with the standard 
> default packages (dovecot-2.3.8, postfix-3.3, ...).
> Now this can be reconsidered. I suppose there will be a RockyLinux or 
> something equivalent but if there is a good reason I can consider Debian 
> or other OS if they have a decent EOL or some advantages.
> 
> Anyway, the more relevant problem at the moment is collect info for the 
> best approch to have a smooth dovecot upgrade.
> 
> My dream is the possibility to configure a new server and rsync the data 
> (/var/mail + /home/users), and, when the tests are satisfiable do the 
> final sync and swap the IP, but I suppose deleting the .imap folders 
> isn't a simple complete solution to compatibility problems.
> 
> Any hints, links, experiences are appreciated.
> 
> Thanks, B.

RE: migration from 2.0.16

[Marc Roos]

 

I would not choose centos 8 it has EOL < than centos7. IBM is pulling 
the plug on the centos distribution, and makes it more or less a beta 
for the rhel. Thus centos7 and then you have a few years to decide what 
to choose. Enough to go to full containerized eg. ;)

You do not need to rsync, dovecot can sync messages. I am just in the 
process of migrating a server from a different network to a different 
mailbox format. 

My approach was to create an 'archive' namespace on shared slower but 
distributed storage so I do not have to move to much data.



-Original Message-
From: Barbara M. [mailto:barb...@rfx.it] 
Sent: 17 December 2020 01:47
To: dovecot@dovecot.org
Subject: migration from 2.0.16


I have an old server with CentOS 6.x and dovecot 2.0.16 (postfix-2.6.6 
and roundcube), that was an update from a 1.x many years ago ...
Users in /etc/passwd
Mailbox format mbox
some filtering via procmail
About 5.000 users, 1 TB data (/var/mail + /home/users)

Obviously I am searching for a smooth upgrade path (with no or minimal 
downtime and users problems) ;-)

Until few days ago my idea was a CentOS 8.x new box with the standard 
default packages (dovecot-2.3.8, postfix-3.3, ...).
Now this can be reconsidered. I suppose there will be a RockyLinux or 
something equivalent but if there is a good reason I can consider Debian 
or other OS if they have a decent EOL or some advantages.

Anyway, the more relevant problem at the moment is collect info for the 
best approch to have a smooth dovecot upgrade.

My dream is the possibility to configure a new server and rsync the data 
(/var/mail + /home/users), and, when the tests are satisfiable do the 
final sync and swap the IP, but I suppose deleting the .imap folders 
isn't a simple complete solution to compatibility problems.

Any hints, links, experiences are appreciated.

Thanks, B.

Re: Migration issue

[Joseph Tam]

On Tue, 4 Aug 2020, Kishore Potnuru wrote:


So, both password files (master and regular user credentials) have the same
contents in this scenario, correct?


No.

Master users are administrative users you allow to authenticate as another
account without having to know their password.  If the master account is
"master", and the user account is "xyz", then an administrator can access
xyz's mail by authenticating as

username: xyz*master
password: password for master

This would allow, for example, to migrate all users via the IMAPC
mechanism without having to know all their passwords.

By making both master and passdb's the same, you allow anyone to access
anybody else's account e.g. "xyz" can access account for "abc" by using
their password with user "abc*xyz".

Joseph Tam 

Re: Migration issue

[Markus Winkler]

Hi Kishore,

On 04.08.20 17:48, Kishore Potnuru wrote:

passdb {
         args = /etc/dovecot/master-users
         driver = passwd-file
         master = yes
         #pass = yes

---^^^
IMHO not important for this case , but in your environment it could be 
better to enable 'pass = yes'



passdb {
     driver = passwd-file
     args = username_format=%u /etc/dovecot/passwd
}

Now I am getting the below Authentication error from production2.


According to your password file, could you please try to change it this way:

passdb {
 driver = passwd-file
 args = scheme=PLAIN username_format=%u /etc/dovecot/passwd
}

AFAIK the default scheme is CRYPT, so I think it's necessary to change it 
with this parameter.



I have copied the same content of the "passwd" file to "master-users" file. 
Actually, it should be having same content? if different, what will be the data and which format?



imapc_password = vmail
imapc_master_user = vmail


To be honest: I'm not sure.

If you want to use a master user then the credentials for 
imapc_master_user/imapc_password have to be in /etc/dovecot/master-users of 
'production1'.


But AFAIK the migration should also work without using a master user (as 
long as you have the credentials of all the users of the old server). I 
hope I'm not wrong. It's been a while since I've done such a migration from 
an old server and cannot remember the details.


HTH and regards,
Markus

Re: Migration issue

[Kishore Potnuru]

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 production2. Seems I
have made some mistake.

-
[root@production2 dovecot]# doveadm backup -a All -R -u
kish...@test.testorg.com imapc:
dsync(kish...@test.testorg.com): Info: imapc(production1.testorg.com:143):
Connected to 161.2.11.119:143 (local xxx.xxx.xxx.xxx:39200)
dsync(kish...@test.testorg.com): Error: imapc(production1.testorg.com:143):
Authentication failed: [AUTHENTICATIONFAILED] Authentication failed.
dsync(kish...@test.testorg.com): Error: User initialization failed: imapc:
Login to production1.testorg.com failed: Authentication failed:
[AUTHENTICATIONFAILED] Authentication failed.
-

In production1, I see this error:

-
Aug 04 16:42:43 imap-login: Info: Disconnected (auth failed, 1 attempts):
user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx
-

The content on the password file:

---
[root@production1 log]# cat /etc/dovecot/passwd
ka...@test.testorg.com:{PLAIN}Password123
kish...@test.testorg.com:{PLAIN}Password123

[root@production1 log]# cat /etc/dovecot/master-users
ka...@test.testorg.com:{PLAIN}Password123
kish...@test.testorg.com:{PLAIN}Password123
---
I have copied the same content of the "passwd" file to "master-users" file.
Actually, it should be having same content? if different, what will be the
data and which format?

Please advise me, what am I making mistakes? As told you before, the
dovecot versions are production1(2.0.9) and production2(2.2.36 (1f10bfa63))


On Tue, Aug 4, 2020 at 11:21 AM Markus Winkler  wrote:

> 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
> }
>
>
> Something similar should work in your case.
>
> Regards,
> Markus
>

Re: Migration issue

[Markus Winkler]

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
}


Something similar should work in your case.

Regards,
Markus

Re: Migration issue

[Kishore Potnuru]

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  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
> 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
> > ===
> >
> > =
> > My old server dovecot.conf (production1):
> > =
> >
> > passdb {
> >args = /etc/dovecot/passwd
> >driver = passwd-file
> >master = yes
> >pass = yes
> >}
>
> My interpretation of your error messages is you need 2 sets of credentials:
> regular users and master users.  You've only supplied master passwords.
> You'll need
>
> # Contains master users credentials
> passdb {
> args = /etc/dovecot/master-passwd
> driver = passwd-file
> master = yes
> pass = yes
> }
>
> # Contains regular user credentials
> passdb {
> args = /etc/dovecot/passwd
> driver = passwd-file
> }
>
> Joseph Tam 
>

Re: Migration issue

[Joseph Tam]

On Mon, 3 Aug 2020, Kishore Potnuru 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
===

=
My old server dovecot.conf (production1):
=

passdb {
   args = /etc/dovecot/passwd
   driver = passwd-file
   master = yes
   pass = yes
   }


My interpretation of your error messages is you need 2 sets of credentials:
regular users and master users.  You've only supplied master passwords.
You'll need

# Contains master users credentials
passdb {
args = /etc/dovecot/master-passwd
driver = passwd-file
master = yes
pass = yes
}

# Contains regular user credentials
passdb {
args = /etc/dovecot/passwd
driver = passwd-file
}

Joseph Tam 

Re: Migration issue

[Kishore Potnuru]

Hi Markus,

Please find the details below and please let me know if you need any other
information.

1) Are users able to login and access their mailboxes on production1 with
an IMAP client?

Ans: Yes.

2)

[root@production1 ~]# ps -ef | grep dovecot
dovecot800 1  0 Jul07 ?00:00:07 dovecot/anvil
root   801 1  0 Jul07 ?00:00:09 dovecot/log
root   804 1  0 Jul07 ?00:00:31 dovecot/config
vmail 1310 1  0 Jul08 ?00:00:00 dovecot/imap
dovecot   1440 1  0 Jul09 ?00:00:07 dovecot/anvil
root  1441 1  0 Jul09 ?00:00:08 dovecot/log
vmail 1473 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 2095 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 2354 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 2584 1  0 Jul09 ?00:00:00 dovecot/imap
dovecot   3001 1  0 Jul08 ?00:00:09 dovecot/anvil
root  3002 1  0 Jul08 ?00:00:11 dovecot/log
vmail 4004 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 4535 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 4546 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 4649 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 4677 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 4913 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 5208 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 5353 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 5799 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 6280 1  0 Jul08 ?00:00:00 dovecot/imap
vmail 6774 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 6975 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 7035 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 9108 1  0 Jul09 ?00:00:00 dovecot/imap
vmail 9741 1  0 Jul07 ?00:00:00 dovecot/imap
vmail10022 1  0 Jul09 ?00:00:00 dovecot/imap
vmail10900 1  0 Jul08 ?00:00:00 dovecot/imap
vmail11522 1  0 Jul09 ?00:00:00 dovecot/imap
vmail11579 1  0 Jul09 ?00:00:00 dovecot/imap
vmail13190 1  0 Jul08 ?00:00:00 dovecot/imap
vmail13837 1  0 Jul09 ?00:00:00 dovecot/imap
vmail15689 1  0 Jul08 ?00:00:00 dovecot/imap
vmail16089 1  0 Jul09 ?00:00:00 dovecot/imap
vmail17919 1  0 Jul08 ?00:00:00 dovecot/imap
vmail18377 1  0 Jul07 ?00:00:00 dovecot/imap
vmail18404 1  0 Jul09 ?00:00:00 dovecot/imap
vmail20279 1  0 Jul08 ?00:00:00 dovecot/imap
vmail20639 1  0 Jul09 ?00:00:00 dovecot/imap
vmail20658 1  0 Jul08 ?00:00:00 dovecot/imap
vmail21397 1  0 Jul07 ?00:00:00 dovecot/imap
dovenull 21624 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21627 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21628 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21633 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21636 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21641 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21644 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21645 1  0 20:18 ?00:00:00 dovecot/pop3-login
dovenull 21789 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21873 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21875 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21878 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21880 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21882 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21884 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21888 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21889 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21891 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21893 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21896 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21897 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21904 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21907 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21920 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21921 1  0 20:19 ?00:00:00 dovecot/pop3-login
dovenull 21927 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21929 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21932 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21933 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21935 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21938 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21942 1  0 20:20 ?00:00:00 dovecot/pop3-login
dovenull 21943 1  0 20:20 ?

Re: Migration issue

[Markus Winkler]

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

Re: Migration issue

[Kishore Potnuru]

Please provide your suggestions to resolve the issue.

On Tue, Jul 28, 2020 at 9:18 PM Kishore Potnuru 
wrote:

>
> 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
> }
> pop3_uidl_format = %g
> protocols = pop3 imap
> ssl = yes
> ssl_cert =  ssl_key = 
> userdb {
> args = uid=vmail gid=vmail home=/z1dev/mail/virtual/%d/%n
> driver = static
> }
> mail_debug = no
> verbose_ssl = no
>
> =
> My New server dovecot.conf(production2):
> =
>
> disable_plaintext_auth = no
>
> listen = *
> log_path = /var/log/dovecot.log
>
> mail_location = maildir:/z1devenv/mail/virtual/%d/%n/Maildir/
>
> passdb {
> args = /etc/dovecot/passwd
> driver = passwd-file
> }
>
> pop3_uidl_format = %g
> protocols = pop3 imap
>
> ssl = yes
> ssl_cert =  ssl_key = 
> userdb {
> args = uid=vmail gid=vmail home=/z1devenv/mail/virtual/%d/%n
> driver = static
> }
>
> 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:vm...@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 = production1.baplc.com
> imapc_password = vmail
> imapc_master_user = vmail
> imapc_user = %u
>
> ===
>
> On Tue, Jul 28, 2020 at 8:44 PM Antonio Leding  wrote:
>
>> 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 
>> wrote:
>>
>> 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@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
>>  imapc:
>> dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
>> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992)
>> dsync(kish...@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(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
>> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014)
>> dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
>> connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting
>> dsync(kish...@test.ba.com): Error: User initialization failed: imapc:
>> Login to production1.baplc.com failed: Disconnected from server
>> [root@production2 log]#
>> --
>>
>> I looked into the production1 (old server) logs. I see the below error.
>>
>> ===
>> 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
>> ===
>>
>> Please suggest me on fixing the issue.
>>
>>
>>
>>

Re: Migration issue

[Kishore Potnuru]

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
}
pop3_uidl_format = %g
protocols = pop3 imap
ssl = yes
ssl_cert =  wrote:

> 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 
> wrote:
>
> 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@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
>  imapc:
> dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992)
> dsync(kish...@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(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014)
> dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
> connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting
> dsync(kish...@test.ba.com): Error: User initialization failed: imapc:
> Login to production1.baplc.com failed: Disconnected from server
> [root@production2 log]#
> --
>
> I looked into the production1 (old server) logs. I see the below error.
>
> ===
> 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
> ===
>
> Please suggest me on fixing the issue.
>
>
>
>

Re: Migration issue

[Antonio Leding]

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  
> wrote:
> 
> 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@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com 
>  imapc:
> dsync(kish...@test.ba.com ): Info: 
> imapc(production1.baplc.com:143 ): 
> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992)
> dsync(kish...@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(kish...@test.ba.com ): Info: 
> imapc(production1.baplc.com:143 ): 
> Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014)
> dsync(kish...@test.ba.com ): Error: 
> imapc(production1.baplc.com:143 ): 
> connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting
> dsync(kish...@test.ba.com ): Error: User 
> initialization failed: imapc: Login to production1.baplc.com 
>  failed: Disconnected from server
> [root@production2 log]#
> --
> 
> I looked into the production1 (old server) logs. I see the below error.
> 
> ===
> 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
> ===
> 
> Please suggest me on fixing the issue.  
>  

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

I have tried the same way as per your suggestion. But it's throwing an
error.

-
[root@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
imapc:
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992)
dsync(kish...@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(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014)
dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting
dsync(kish...@test.ba.com): Error: User initialization failed: imapc: Login
to production1.baplc.com failed: Disconnected from server
[root@production2 log]#
--

I looked into the production1 (old server) logs. I see the below error.

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

Please suggest me on fixing the issue.

On Tue, Jul 28, 2020 at 6:57 AM Aki Tuomi 
wrote:

> 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 let you pull the mails from the old host to your new host over
> IMAP.
>
> You should probably also look at
>
> https://wiki.dovecot.org/Migration/Dsync
>
> Aki
>
> > On 28/07/2020 03:02 Antonio Leding  wrote:
> >
> >
> > 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
> > https://dovecot.org/list/dovecot/2012-March/134110.html
> >
> > Also, mention of a working syntax for the remote side command can be
> found in this post:
> >
> > https://dovecot.org/list/dovecot/2012-February/081425.html
> >
> > I’m sure one of the Dovecot devs will chime in at some point but in the
> meantime, hopefully the above will offer some relief…
> >
> >
> >
> >
> > > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > >
> > >
> > > 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.reac...@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, 
> wrote:
> > > > > 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 ]  []
> > > > >
> > > > > altmove [-u |-A] [-S ] [-r] 
> > > > > auth cache|test
> > > > > backup [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
> > > > > batch [-u |-A] [-S ]   [ 
> [..]]
> > > > > config [doveconf parameters]
> > > > > copy [-u |-A] [-S ]  [user  user>] 
> > > > > director add|dump|flush|map|move|remove|ring|ring|ring|status
> > > > > dump [-t ] 
> > > > > exec  [binary parameters]
> > > > > expunge [-u |-A] [-S ] [-d] 
> > > > > 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

I have tried the same way as per your suggestion. But it's throwing the
below error.

-
[root@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
imapc:
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to 161.2.11.119:143 (local 161.2.12.152:45992)
dsync(kish...@test.ba.com): Warning: imapc(production1.baplc.com:143):
connect(161.2.11.119, 143) timed out after 30 seconds - reconnecting (delay
0 ms)
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to 161.2.11.119:143 (local 161.2.12.152:46014)
dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
connect(161.2.11.119, 143) timed out after 30 seconds - disconnecting
dsync(kish...@test.ba.com): Error: User initialization failed: imapc: Login
to production1.baplc.com failed: Disconnected from server
[root@production2 log]#
--

I looked into the production1 (old server) logs. I see the below error.

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

Please suggest me on fixing the issue. I have also copied the dovecot.conf
from both the servers below.

=
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
}
pop3_uidl_format = %g
protocols = pop3 imap
ssl = yes
ssl_cert = 
wrote:

> 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 let you pull the mails from the old host to your new host over
> IMAP.
>
> You should probably also look at
>
> https://wiki.dovecot.org/Migration/Dsync
>
> Aki
>
> > On 28/07/2020 03:02 Antonio Leding  wrote:
> >
> >
> > 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
> > https://dovecot.org/list/dovecot/2012-March/134110.html
> >
> > Also, mention of a working syntax for the remote side command can be
> found in this post:
> >
> > https://dovecot.org/list/dovecot/2012-February/081425.html
> >
> > I’m sure one of the Dovecot devs will chime in at some point but in the
> meantime, hopefully the above will offer some relief…
> >
> >
> >
> >
> > > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > >
> > >
> > > 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.reac...@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, 
> wrote:
> > > > > 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 

Re: Migration from one server to 2 new servers

[Aki Tuomi]

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 let you pull the mails from the old host to your new host over 
IMAP. 

You should probably also look at

https://wiki.dovecot.org/Migration/Dsync

Aki

> On 28/07/2020 03:02 Antonio Leding  wrote:
> 
> 
> 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
> https://dovecot.org/list/dovecot/2012-March/134110.html
> 
> Also, mention of a working syntax for the remote side command can be found in 
> this post:
> 
> https://dovecot.org/list/dovecot/2012-February/081425.html
> 
> I’m sure one of the Dovecot devs will chime in at some point but in the 
> meantime, hopefully the above will offer some relief…
> 
> 
> 
> 
> > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > 
> > 
> > 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  
> > > 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,  wrote:
> > > > 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 ]  []
> > > > 
> > > > altmove [-u |-A] [-S ] [-r] 
> > > > auth cache|test
> > > > backup [-u |-A] [-S ] [-dfR] [-l ] [-m 
> > > > ] [-n ] [-s ] 
> > > > batch [-u |-A] [-S ]   [  [..]]
> > > > config [doveconf parameters]
> > > > copy [-u |-A] [-S ]  [user  > > > user>] 
> > > > director add|dump|flush|map|move|remove|ring|ring|ring|status
> > > > dump [-t ] 
> > > > exec  [binary parameters]
> > > > expunge [-u |-A] [-S ] [-d] 
> > > > fetch [-u |-A] [-S ]  
> > > > force-resync [-u |-A] [-S ] 
> > > > fs copy|delete|get|iter|iter-dirs|put|stat
> > > > help 
> > > > import [-u |-A] [-S ] [-s]  
> > > >  
> > > > index [-u |-A] [-S ] [-q] [-n ]  > > > mask>
> > > > instance list|remove
> > > > kick [-a ] [-f] [|]
> > > > log errors|find|reopen|test
> > > > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> > > > mount add|list|remove
> > > > move [-u |-A] [-S ]  [user  > > > user>] 
> > > > penalty [-a ] []
> > > > proxy kick|list
> > > > purge [-u |-A] [-S ]
> > > > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V]
> > > > reload
> > > > replicator remove|replicate|status
> > > > search [-u |-A] [-S ] 
> > > > sis deduplicate|find
> > > > stats dump|top
> > > > stop
> > > > sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
> > > > ] [-n ] [-s ] 
> > > > user [-a ] [-x ] [-f field] [-u]  > > > mask> [...]
> > > > who [-a ] [-1] [] []
> > > > zlibconnect  []
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > On Jul 27, 2020, at 3:28 PM, Kishore Potnuru 
> > > > >  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@production2 ~]# dovecot --version
> > > > > > 2.2.36 (1f10bfa63)
> > > > > > 
> > > > > > 
> > > > > > The old version is : 
> > > > > > ==
> > > > > > [root@production1 ~]# dovecot --version
> > > > > > 2.0.9
> > > > > > 
> > > > > > 
> > > > > > I have executed the command 

Re: Migration from one server to 2 new servers

[Antonio Leding]

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 

https://dovecot.org/list/dovecot/2012-March/134110.html 


Also, mention of a working syntax for the remote side command can be found in 
this post:  

https://dovecot.org/list/dovecot/2012-February/081425.html 


I’m sure one of the Dovecot devs will chime in at some point but in the 
meantime, hopefully the above will offer some relief…



> On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> 
> 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 > > 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, > > wrote:
>> 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 ]  []
>> 
>>   altmove  [-u |-A] [-S ] [-r] 
>>   auth cache|test
>>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
>> ] [-n ] [-s ] 
>>   batch[-u |-A] [-S ]   [  
>> [..]]
>>   config   [doveconf parameters]
>>   copy [-u |-A] [-S ]  [user > user>] 
>>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>>   dump [-t ] 
>>   exec  [binary parameters]
>>   expunge  [-u |-A] [-S ] [-d] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   fs   copy|delete|get|iter|iter-dirs|put|stat
>>   help 
>>   import   [-u |-A] [-S ] [-s]  
>>  
>>   index[-u |-A] [-S ] [-q] [-n ] 
>> 
>>   instance list|remove
>>   kick [-a ] [-f] [|]
>>   log  errors|find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   mountadd|list|remove
>>   move [-u |-A] [-S ]  [user > user>] 
>>   penalty  [-a ] []
>>   proxykick|list
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u 
>> user] [-V]
>>   reload
>>   replicator   remove|replicate|status
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   statsdump|top
>>   stop
>>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
>> ] [-n ] [-s ] 
>>   user [-a ] [-x ] [-f field] [-u] 
>>  [...]
>>   who  [-a ] [-1] [] []
>>   zlibconnect   []
>> 
>> 
>>> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru >> > 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@production2 ~]# dovecot --version
>>> 2.2.36 (1f10bfa63)
>>> 
>>> 
>>> The old version is : 
>>> ==
>>> [root@production1 ~]# dovecot --version
>>> 2.0.9
>>> 
>>> 
>>> I have executed the command from the new server:
>>> 
>>> 
>>> 
>>> =
>>> [root@production2 test.org.com ]# doveadm backup -R 
>>> -u kish...@test.org.com  
>>> remote:vm...@production1.baplc.com 
>>> 
>>> vm...@production1.baplc.com 's password:
>>> usage: doveadm [-Dv] [-f ]  []
>>> 
>>>   altmove  [-u |-A] [-S ] 
>>>   auth [-a ] [-x ]  []
>>>   config   [doveconf parameters]
>>>   director add|flush|map|remove|status
>>>   dump [-t ] 
>>>   expunge  [-u |-A] [-S ] 
>>>   fetch   

Re: Migration from one server to 2 new servers

[Antonio Leding]

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  
> 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,  > wrote:
> 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 ]  []
> 
>   altmove  [-u |-A] [-S ] [-r] 
>   auth cache|test
>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
> ] [-n ] [-s ] 
>   batch[-u |-A] [-S ]   [  
> [..]]
>   config   [doveconf parameters]
>   copy [-u |-A] [-S ]  [user  user>] 
>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>   dump [-t ] 
>   exec  [binary parameters]
>   expunge  [-u |-A] [-S ] [-d] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   fs   copy|delete|get|iter|iter-dirs|put|stat
>   help 
>   import   [-u |-A] [-S ] [-s]  
>  
>   index[-u |-A] [-S ] [-q] [-n ] 
> 
>   instance list|remove
>   kick [-a ] [-f] [|]
>   log  errors|find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   mountadd|list|remove
>   move [-u |-A] [-S ]  [user  user>] 
>   penalty  [-a ] []
>   proxykick|list
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u 
> user] [-V]
>   reload
>   replicator   remove|replicate|status
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   statsdump|top
>   stop
>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
> ] [-n ] [-s ] 
>   user [-a ] [-x ] [-f field] [-u] 
>  [...]
>   who  [-a ] [-1] [] []
>   zlibconnect   []
> 
> 
>> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru > > 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@production2 ~]# dovecot --version
>> 2.2.36 (1f10bfa63)
>> 
>> 
>> The old version is : 
>> ==
>> [root@production1 ~]# dovecot --version
>> 2.0.9
>> 
>> 
>> I have executed the command from the new server:
>> 
>> 
>> 
>> =
>> [root@production2 test.org.com ]# doveadm backup -R -u 
>> kish...@test.org.com  
>> remote:vm...@production1.baplc.com 
>> 
>> vm...@production1.baplc.com 's password:
>> usage: doveadm [-Dv] [-f ]  []
>> 
>>   altmove  [-u |-A] [-S ] 
>>   auth [-a ] [-x ]  []
>>   config   [doveconf parameters]
>>   director add|flush|map|remove|status
>>   dump [-t ] 
>>   expunge  [-u |-A] [-S ] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   help 
>>   import   [-u |-A] [-S ]  
>>  
>>   kick [-a ] [-f] [|]
>>   log  find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   penalty  [-a ] []
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>>   reload
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   stop
>>   user [-a ] [-x ]  [...]
>>   who  [-a ] [-1] [] []
>> dsync-local(kish...@test.org.com ): Error: 
>> read(vm...@production1.baplc.com ) 
>> failed: EOF (version not received)
>> dsync-local(kish...@test.org.com ): Error: 
>> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>>  doveadm dsync-server -ukish...@test.org.com 
>> 
>> 
>> [root@production2 test.org.com ]#
>> 
>> =
>> 
>> 
>> On 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

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

> 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 ]  []
>
>   altmove  [-u |-A] [-S ] [-r] 
>   auth cache|test
>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
>   batch[-u |-A] [-S ]   [
>  [..]]
>   config   [doveconf parameters]
>   copy [-u |-A] [-S ]  [user
> ] 
>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>   dump [-t ] 
>   exec  [binary parameters]
>   expunge  [-u |-A] [-S ] [-d] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   fs   copy|delete|get|iter|iter-dirs|put|stat
>   help 
>   import   [-u |-A] [-S ] [-s]  location>  
>   index[-u |-A] [-S ] [-q] [-n ]
> 
>   instance list|remove
>   kick [-a ] [-f] [|]
>   log  errors|find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   mountadd|list|remove
>   move [-u |-A] [-S ]  [user
> ] 
>   penalty  [-a ] []
>   proxykick|list
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u
> user] [-V]
>   reload
>   replicator   remove|replicate|status
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   statsdump|top
>   stop
>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
>   user [-a ] [-x ] [-f field] [-u]
>  [...]
>   who  [-a ] [-1] [] []
>   zlibconnect   []
>
>
> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru 
> 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@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
>
>
> The old version is :
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
>
>
> I have executed the command from the new server:
>
>
>
> =
> [root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
>  remote:vm...@production1.baplc.com
> vm...@production1.baplc.com's password:
> usage: doveadm [-Dv] [-f ]  []
>
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ] 
>  
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com): Error: Remote command returned error
> 1: ssh -lvmail production1.baplc.com doveadm dsync-server -
> ukish...@test.org.com
>
> [root@production2 test.org.com]#
>
> =
>
>
>
> On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  wrote:
>
>> 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
>> pulling from the remote of prod2…
>>
>>
>>
>>
>>
>>
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru 
>> wrote:
>>
>> 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
>> 

Re: Migration from one server to 2 new servers

[Antonio Leding]

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 ]  []

  altmove  [-u |-A] [-S ] [-r] 
  auth cache|test
  backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
] [-n ] [-s ] 
  batch[-u |-A] [-S ]   [  
[..]]
  config   [doveconf parameters]
  copy [-u |-A] [-S ]  [user ] 
  director add|dump|flush|map|move|remove|ring|ring|ring|status
  dump [-t ] 
  exec  [binary parameters]
  expunge  [-u |-A] [-S ] [-d] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  fs   copy|delete|get|iter|iter-dirs|put|stat
  help 
  import   [-u |-A] [-S ] [-s]  
 
  index[-u |-A] [-S ] [-q] [-n ] 

  instance list|remove
  kick [-a ] [-f] [|]
  log  errors|find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  mountadd|list|remove
  move [-u |-A] [-S ]  [user ] 
  penalty  [-a ] []
  proxykick|list
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] 
[-V]
  reload
  replicator   remove|replicate|status
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  statsdump|top
  stop
  sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
] [-n ] [-s ] 
  user [-a ] [-x ] [-f field] [-u]  [...]
  who  [-a ] [-1] [] []
  zlibconnect   []


> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru  
> 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@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
> 
> 
> The old version is : 
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
> 
> 
> I have executed the command from the new server:
> 
> 
> 
> =
> [root@production2 test.org.com ]# doveadm backup -R -u 
> kish...@test.org.com  
> remote:vm...@production1.baplc.com 
> 
> vm...@production1.baplc.com 's password:
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com ): Error: 
> read(vm...@production1.baplc.com ) 
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com ): Error: 
> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>  doveadm dsync-server -ukish...@test.org.com 
> 
> 
> [root@production2 test.org.com ]#
> 
> =
> 
> 
> On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  > wrote:
> 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 pulling from 
> the remote of prod2…
> 
> 
> 
> 
> 
> 
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru > > wrote:
>> 
>> 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 
>> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

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


The old version is :
==
[root@production1 ~]# dovecot --version
2.0.9


I have executed the command from the new server:



=
[root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production1.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com

[root@production2 test.org.com]#

=



On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  wrote:

> 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
> pulling from the remote of prod2…
>
>
>
>
>
>
> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru 
> wrote:
>
> 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 new version is:
> 
> [root@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
>
>
> The old version is :
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
>
>
> I have executed the command from the new server:
>
>
>
> =
> [root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
> remote:vm...@production1.baplc.com
> vm...@production1.baplc.com's password:
> usage: doveadm [-Dv] [-f ]  []
>
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ] 
>  
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com): Error: Remote command returned error
> 1: ssh -lvmail production1.baplc.com doveadm dsync-server -
> ukish...@test.org.com
>
> [root@production2 test.org.com]#
>
> =
>
> On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  wrote:
>
>> Not sure if this matters but the prompt when attempting the “doveadm
>> backup” command shows it to be a “production" server…
>>
>> [root at production1  
>> test.org.com]# doveadm backup -R -u kishore at test.org.com 
>> 
>> remote:vmail at production2.baplc.com 
>> 
>>
>>
>> ...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 

Re: Migration from one server to 2 new servers

[Antonio Leding]

Also, FWIW...your doveadm command is missing quite a few options…here is mine…

[Jul-27 @ 15:11:57] > dovecot —version
2.3.10.1 (a3d0e1171)

[Jul-27 @ 15:22:39] > ls -l /usr/bin/doveadm
-rwxr-xr-x. 1 root root 2949584 May 19 02:09 /usr/bin/doveadm

[Jul-27 @ 15:21:31] > doveadm
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] [-r] 
  auth cache|login|lookup|test
  backup   [-u |-A] [-S ] [-fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|
  batch[-u |-A] [-S ]   [  
[..]]
  config   [doveconf parameters]
  copy [-u |-A] [-S ]  [user ] 
  deduplicate  [-u |-A] [-S ] [-m] 
  dict get|inc|iter|set|unset
  director add|down|dump|flush|kick|map|move|remove|ring|status|up|update
  dump [-t ] 
  exec  [binary parameters]
  expunge  [-u |-A] [-S ] [-m] 
  fetch[-u |-A] [-S ]  
  flagsadd|remove|replace
  force-resync [-u |-A] [-S ] [-f] 
  fs   copy|delete|get|iter|iter-dirs|metadata|put|stat
  help 
  import   [-u |-A] [-S ] [-U source-user] [-s]   
  index[-u |-A] [-S ] [-q] [-n ] 

  instance list|remove
  kick [-a ] [|]
  log  errors|find|reopen|test
  mailbox  
cache|cache|create|delete|list|metadata|mutf7|path|rename|status|subscribe|unsubscribe|update
  move [-u |-A] [-S ]  [user ] 
  oldstats dump|reset|top
  penalty  [-a ] []
  process  status
  proxykick|list
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] 
[-V]
  rebuild  attachments
  reload
  replicator   add|dsync-status|remove|replicate|status
  save [-u |-A] [-S ] [-m mailbox]
  search   [-u |-A] [-S ] 
  service  status|stop
  sieveactivate|deactivate|delete|get|list|put|rename
  sis  deduplicate|find
  statsdump
  stop
  sync [-u |-A] [-S ] [-1fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|
  user [-a ] [-x ] [-f field] [-e 
] [-u]  [...]
  who  [-a ] [-1] [] []
  zlibconnect   []


> On Jul 27, 2020, at 3:18 PM, Antonio Leding  wrote:
> 
> 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 pulling from 
> the remote of prod2…
> 
> 
> 
> 
> 
> 
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru > > wrote:
>> 
>> 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@production2 ~]# dovecot --version
>> 2.2.36 (1f10bfa63)
>> 
>> 
>> The New version is : 
>> ==
>> [root@production1 ~]# dovecot --version
>> 2.0.9
>> 
>> 
>> I have executed the command from the new server:
>> 
>> 
>> 
>> =
>> [root@production2 test.org.com ]# doveadm backup -R -u 
>> kish...@test.org.com  
>> remote:vm...@production1.baplc.com 
>> 
>> vm...@production1.baplc.com 's password:
>> usage: doveadm [-Dv] [-f ]  []
>> 
>>   altmove  [-u |-A] [-S ] 
>>   auth [-a ] [-x ]  []
>>   config   [doveconf parameters]
>>   director add|flush|map|remove|status
>>   dump [-t ] 
>>   expunge  [-u |-A] [-S ] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   help 
>>   import   [-u |-A] [-S ]  
>>  
>>   kick [-a ] [-f] [|]
>>   log  find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   penalty  [-a ] []
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>>   reload
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   stop
>>   user [-a ] [-x ]  [...]
>>   who  [-a ] [-1] [] []
>> dsync-local(kish...@test.org.com ): Error: 
>> read(vm...@production1.baplc.com ) 
>> failed: EOF (version not received)
>> dsync-local(kish...@test.org.com ): Error: 
>> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>>  doveadm 

Re: Migration from one server to 2 new servers

[Antonio Leding]

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 pulling from the 
remote of prod2…






> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru  
> wrote:
> 
> 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@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
> 
> 
> The New version is : 
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
> 
> 
> I have executed the command from the new server:
> 
> 
> 
> =
> [root@production2 test.org.com ]# doveadm backup -R -u 
> kish...@test.org.com  
> remote:vm...@production1.baplc.com 
> 
> vm...@production1.baplc.com 's password:
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com ): Error: 
> read(vm...@production1.baplc.com ) 
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com ): Error: 
> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>  doveadm dsync-server -ukish...@test.org.com 
> 
> 
> [root@production2 test.org.com ]#
> 
> =
> 
> On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  > wrote:
> Not sure if this matters but the prompt when attempting the “doveadm backup” 
> command shows it to be a “production" server…
> 
> [root at production1  
> test.org.com ]# doveadm backup -R -u kishore at 
> test.org.com 
> remote:vmail at production2.baplc.com 
> 
> 
> ...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:50 PM, Sami Ketola > > wrote:
>> 
>> 
>> 
>>> On 28. Jul 2020, at 0.10, Kishore Potnuru >> > wrote:
>>> 
>>> Yes. Please find the details of the servers below. I am executing the 
>>> command from one of the new servers.
>> 
>> I find it very hard to believe this. Shall I look at the version control 
>> when backup was added as option to doveadm?
>> 
>> 2.2.36 has it:
>> 
>> [root@ketola ~]# dovecot --version
>> 2.2.36.8 (0c9d56b41)
>> [root@ketola ~]# doveadm backup
>> doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r 
>> ] [-m ] [-g ] [-n  | -N] [-x 
>> ] [-s ] [-t ] -d|
>> 
>> 
>> Sami
>> 
>> 
> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

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


The New version is :
==
[root@production1 ~]# dovecot --version
2.0.9


I have executed the command from the new server:



=
[root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production1.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com

[root@production2 test.org.com]#

=

On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  wrote:

> Not sure if this matters but the prompt when attempting the “doveadm
> backup” command shows it to be a “production" server…
>
> [root at production1  
> test.org.com]# doveadm backup -R -u kishore at test.org.com 
> 
> remote:vmail at production2.baplc.com 
> 
>
>
> ...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:50 PM, Sami Ketola  wrote:
>
>
>
> On 28. Jul 2020, at 0.10, Kishore Potnuru 
> wrote:
>
> Yes. Please find the details of the servers below. I am executing the
> command from one of the new servers.
>
>
> I find it very hard to believe this. Shall I look at the version control
> when backup was added as option to doveadm?
>
> 2.2.36 has it:
>
> [root@ketola ~]# dovecot --version
> 2.2.36.8 (0c9d56b41)
> [root@ketola ~]# doveadm backup
> doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r
> ] [-m ] [-g ] [-n  | -N] [-x
> ] [-s ] [-t ] -d|
>
>
> Sami
>
>
>
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

> On 28. Jul 2020, at 0.10, Kishore Potnuru  wrote:
> 
> Yes. Please find the details of the servers below. I am executing the command 
> from one of the new servers.

I find it very hard to believe this. Shall I look at the version control when 
backup was added as option to doveadm?

2.2.36 has it:

[root@ketola ~]# dovecot --version
2.2.36.8 (0c9d56b41)
[root@ketola ~]# doveadm backup
doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|


Sami

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

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 Linux Server release 7.7 (Maipo)
Dovecot version -  2.2.36 (1f10bfa63)
Postfix version -  2.10.1
==

Thanks & Regards,
Kishore

On Mon, 27 Jul, 2020, 9:43 pm Sami Ketola,  wrote:

>
>
> > On 27. Jul 2020, at 23.11, Kishore Potnuru 
> wrote:
> >
> > Hi ,
> >
> > I have tried the below command from the new server. But I am getting an
> error. Anything is missing here?
> >
>
> Are you sure that is dovecot 2.2.36?
>
> Sami
>
>
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

> On 27. Jul 2020, at 23.11, Kishore Potnuru  wrote:
> 
> Hi ,
> 
> I have tried the below command from the new server. But I am getting an 
> error. Anything is missing here?
> 

Are you sure that is dovecot 2.2.36?

Sami

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi ,

I have tried the below command from the new server. But I am getting an
error. Anything is missing here?


[root@production1 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production2.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com
[root@production1 test.org.com]#



On Mon, Jul 27, 2020 at 3:08 PM Aki Tuomi 
wrote:

> No, but there is backup option on the new server. That's why the -R, which
> means "backup to here".
>
> Aki
>
> > On 27/07/2020 16:20 Kishore Potnuru  wrote:
> >
> >
> > Hi,
> >
> > But there is no "doveadm backup" option in dovecot 2.0.9 version.
> >
> > [root@production ~]# doveadm -backup
> > doveadm: invalid option -- 'b'
> > [root@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 
> wrote:
> > >
> > >  > On 27/07/2020 11:59 Kishore Potnuru 
> 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
> > >  > Postfix version - 2.6.6
> > >  > 
> > >  >
> > >  > New Servers:
> > >  > ==
> > >  > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > >  > Dovecot version - 2.2.36 (1f10bfa63)
> > >  > Postfix version - 2.10.1
> > >  > ==
> > >  >
> > >  > What is the best way to stop/copy/migrate the current production
> data to the new servers? I am planning the following steps. Not sure if it
> is correct or not.
> > >  >
> > >  > 1. Stop the Postfix services on the old server and wait for few
> mins. So that no new emails will be coming to the old servers. Existing
> emails will be delivered to the receipients.
> > >  >
> > >  > 2. copy/migrate the data from old server to new servers. Please
> suggest what is the best way?
> > >  >
> > >  > 3. I see that dovecot version(2.0.9) in old production server, I do
> not know the which is the best option? see the options in the current
> version.
> > >  >
> > >  > =
> > >  > [root@prodcution ~]# doveadm
> > >  > usage: doveadm [-Dv] [-f ]  []
> > >  >
> > >  > altmove [-u |-A] [-S ] 
> > >  > auth [-a ] [-x ]  []
> > >  > config [doveconf parameters]
> > >  > director add|flush|map|remove|status
> > >  > dump [-t ] 
> > >  > expunge [-u |-A] [-S ] 
> > >  > fetch [-u |-A] [-S ]  
> > >  > force-resync [-u |-A] [-S ] 
> > >  > help 
> > >  > import [-u |-A] [-S ] 
>  
> > >  > kick [-a ] [-f] [|]
> > >  > log find|reopen|test
> > >  > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> > >  > penalty [-a ] []
> > >  > purge [-u |-A] [-S ]
> > >  > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> > >  > reload
> > >  > search [-u |-A] [-S ] 
> > >  > sis deduplicate|find
> > >  > stop
> > >  > user [-a ] [-x ]  [...]
> > >  >
> > >  > =
> > >  >
> > >  > Please suggest me.
> > >  >
> > >  > Thanks,
> > >  > Kishore Potnuru
> > >
> > >  `doveadm backup -R -u someone imapc:` comes to mind, with master
> password/master user authentication.
> > >
> > >  Aki
> > >
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

Hi,

the idea was to run it on the new server and not on the old server.
That is also why you should use -R parameter to pull the mails from remote, not 
push.

Sami


> On 27. Jul 2020, at 17.13, Kishore Potnuru  wrote:
> 
> 
> I tried this command also. It didn't work. It shows syntax again. Please see 
> the supported commands in dovecot 2.0.9 version. This doesn't support 
> replication also as per syntax, if i am not wrong. Please suggest me. 
> 
> [root@production ~]# doveadm backup -u kish...@test.org.com 
>  remote:vm...@production2.test.org.com 
> 
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> 
> 
> On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  
> mailto:ad...@dishaw.org>> wrote:
> 
> 
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  > > 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.
> > 
> 
> I recently did a similar move
> 
> > 
> > What is the best way to stop/copy/migrate the current production data to 
> > the new servers? I am planning the following steps. Not sure if it is 
> > correct or not.
> > 
> 
> Step 0.
> 
> Setup replication and have mail replicate from the old servers to the new 
> servers.
> 
> > 1. Stop the Postfix services on the old server and wait for few mins. So 
> > that no new emails will be coming to the old servers. Existing emails will 
> > be delivered to the receipients.
> > 
> 
> I stopped Postfix on the old servers and did not start Postfix on the new 
> servers.  I waited until I saw that no mail was replicating from the old 
> Dovecot to the new servers.
> 
> > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> 
> Using the replication mechanism was the best method for me.
> 
> 

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 10:13 AM, Kishore Potnuru  
> wrote:
> 
> 
> I tried this command also. It didn't work. It shows syntax again. Please see 
> the supported commands in dovecot 2.0.9 version. This doesn't support 
> replication also as per syntax, if i am not wrong. Please suggest me. 
> 
> [root@production ~]# doveadm backup -u kish...@test.org.com 
>  remote:vm...@production2.test.org.com 
> 

I’ve only used the tcps destination, not the remote.  I don’t have 2.0.x on any 
machines, so I can’t test—have you checked the man page (man doveadm-backup)?  
To the best of my knowledge, Dsync existed in 2.0.x.

If you setup tcps, make sure you create a CA and certificates for the two 
servers.  If you don’t want to do that and want to use tcp, either do that on a 
local network or tunnel the connection through SSH.

 
> 
> 
> On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  
> mailto:ad...@dishaw.org>> wrote:
> 
> 
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  > > 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.
> > 
> 
> I recently did a similar move
> 
> > 
> > What is the best way to stop/copy/migrate the current production data to 
> > the new servers? I am planning the following steps. Not sure if it is 
> > correct or not.
> > 
> 
> Step 0.
> 
> Setup replication and have mail replicate from the old servers to the new 
> servers.
> 
> > 1. Stop the Postfix services on the old server and wait for few mins. So 
> > that no new emails will be coming to the old servers. Existing emails will 
> > be delivered to the receipients.
> > 
> 
> I stopped Postfix on the old servers and did not start Postfix on the new 
> servers.  I waited until I saw that no mail was replicating from the old 
> Dovecot to the new servers.
> 
> > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> 
> Using the replication mechanism was the best method for me.
> 
> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

I tried this command also. It didn't work. It shows syntax again. Please
see the supported commands in dovecot 2.0.9 version. This doesn't support
replication also as per syntax, if i am not wrong. Please suggest me.

[root@production ~]# doveadm backup -u kish...@test.org.com
remote:vm...@production2.test.org.com
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []


On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  wrote:

>
>
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru 
> 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.
> >
>
> I recently did a similar move
>
> >
> > What is the best way to stop/copy/migrate the current production data to
> the new servers? I am planning the following steps. Not sure if it is
> correct or not.
> >
>
> Step 0.
>
> Setup replication and have mail replicate from the old servers to the new
> servers.
>
> > 1. Stop the Postfix services on the old server and wait for few mins. So
> that no new emails will be coming to the old servers. Existing emails will
> be delivered to the receipients.
> >
>
> I stopped Postfix on the old servers and did not start Postfix on the new
> servers.  I waited until I saw that no mail was replicating from the old
> Dovecot to the new servers.
>
> > 2. copy/migrate the data from old server to new servers. Please suggest
> what is the best way?
>
> Using the replication mechanism was the best method for me.
>
>
>

Re: Migration from one server to 2 new servers

[Aki Tuomi]

No, but there is backup option on the new server. That's why the -R, which 
means "backup to here".

Aki

> On 27/07/2020 16:20 Kishore Potnuru  wrote:
> 
> 
> Hi,
> 
> But there is no "doveadm backup" option in dovecot 2.0.9 version.
> 
> [root@production ~]# doveadm -backup
> doveadm: invalid option -- 'b'
> [root@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  wrote:
> > 
> >  > On 27/07/2020 11:59 Kishore Potnuru  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
> >  > Postfix version - 2.6.6
> >  > 
> >  > 
> >  > New Servers:
> >  > ==
> >  > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> >  > Dovecot version - 2.2.36 (1f10bfa63)
> >  > Postfix version - 2.10.1 
> >  > ==
> >  > 
> >  > What is the best way to stop/copy/migrate the current production data to 
> > the new servers? I am planning the following steps. Not sure if it is 
> > correct or not.
> >  > 
> >  > 1. Stop the Postfix services on the old server and wait for few mins. So 
> > that no new emails will be coming to the old servers. Existing emails will 
> > be delivered to the receipients.
> >  > 
> >  > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> >  > 
> >  > 3. I see that dovecot version(2.0.9) in old production server, I do not 
> > know the which is the best option? see the options in the current version.
> >  > 
> >  > =
> >  > [root@prodcution ~]# doveadm
> >  > usage: doveadm [-Dv] [-f ]  []
> >  > 
> >  > altmove [-u |-A] [-S ] 
> >  > auth [-a ] [-x ]  []
> >  > config [doveconf parameters]
> >  > director add|flush|map|remove|status
> >  > dump [-t ] 
> >  > expunge [-u |-A] [-S ] 
> >  > fetch [-u |-A] [-S ]  
> >  > force-resync [-u |-A] [-S ] 
> >  > help 
> >  > import [-u |-A] [-S ]   > parent mailbox> 
> >  > kick [-a ] [-f] [|]
> >  > log find|reopen|test
> >  > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  > penalty [-a ] []
> >  > purge [-u |-A] [-S ]
> >  > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  > reload
> >  > search [-u |-A] [-S ] 
> >  > sis deduplicate|find
> >  > stop
> >  > user [-a ] [-x ]  [...]
> >  > 
> >  > =
> >  > 
> >  > Please suggest me.
> >  > 
> >  > Thanks,
> >  > Kishore Potnuru
> >  
> >  `doveadm backup -R -u someone imapc:` comes to mind, with master 
> > password/master user authentication.
> >  
> >  Aki
> >

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 9:20 AM, Kishore Potnuru  
> wrote:
> 
> Hi,
> 
> But there is no "doveadm backup" option in dovecot 2.0.9 version. 
> 
> [root@production ~]# doveadm -backup
> doveadm: invalid option -- 'b'
> [root@production ~]# dovecot --version
> 2.0.9

The command is "doveadm backup”. 

> 
> Copy the contents by using "scp", will that work?
> 

I would recommend against that approach unless you know what you are doing.

> Thanks,
> Kishore Potnuru
> 
> On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi  > wrote:
> 
> > On 27/07/2020 11:59 Kishore Potnuru  > > 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
> > Postfix version - 2.6.6
> > 
> > 
> > New Servers:
> > ==
> > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > Dovecot version - 2.2.36 (1f10bfa63)
> > Postfix version - 2.10.1 
> > ==
> > 
> > What is the best way to stop/copy/migrate the current production data to 
> > the new servers? I am planning the following steps. Not sure if it is 
> > correct or not.
> > 
> > 1. Stop the Postfix services on the old server and wait for few mins. So 
> > that no new emails will be coming to the old servers. Existing emails will 
> > be delivered to the receipients.
> > 
> > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> > 
> > 3. I see that dovecot version(2.0.9) in old production server, I do not 
> > know the which is the best option? see the options in the current version.
> > 
> > =
> > [root@prodcution ~]# doveadm
> > usage: doveadm [-Dv] [-f ]  []
> > 
> >  altmove [-u |-A] [-S ] 
> >  auth [-a ] [-x ]  []
> >  config [doveconf parameters]
> >  director add|flush|map|remove|status
> >  dump [-t ] 
> >  expunge [-u |-A] [-S ] 
> >  fetch [-u |-A] [-S ]  
> >  force-resync [-u |-A] [-S ] 
> >  help 
> >  import [-u |-A] [-S ]   > parent mailbox> 
> >  kick [-a ] [-f] [|]
> >  log find|reopen|test
> >  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  penalty [-a ] []
> >  purge [-u |-A] [-S ]
> >  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  reload
> >  search [-u |-A] [-S ] 
> >  sis deduplicate|find
> >  stop
> >  user [-a ] [-x ]  [...]
> > 
> > =
> > 
> > Please suggest me.
> > 
> > Thanks,
> > Kishore Potnuru
> 
> `doveadm backup -R -u someone imapc:` comes to mind, with master 
> password/master user authentication.
> 
> Aki

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  
> 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.
> 

I recently did a similar move

> 
> What is the best way to stop/copy/migrate the current production data to the 
> new servers? I am planning the following steps. Not sure if it is correct or 
> not.
> 

Step 0.

Setup replication and have mail replicate from the old servers to the new 
servers.

> 1. Stop the Postfix services on the old server and wait for few mins. So that 
> no new emails will be coming to the old servers. Existing emails will be 
> delivered to the receipients.
> 

I stopped Postfix on the old servers and did not start Postfix on the new 
servers.  I waited until I saw that no mail was replicating from the old 
Dovecot to the new servers.

> 2. copy/migrate the data from old server to new servers. Please suggest what 
> is the best way?

Using the replication mechanism was the best method for me.

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

But there is no "doveadm backup" option in dovecot 2.0.9 version.

[root@production ~]# doveadm -backup
doveadm: invalid option -- 'b'
[root@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 
wrote:

>
> > On 27/07/2020 11:59 Kishore Potnuru  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
> > Postfix version - 2.6.6
> > 
> >
> > New Servers:
> > ==
> > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > Dovecot version - 2.2.36 (1f10bfa63)
> > Postfix version - 2.10.1
> > ==
> >
> > What is the best way to stop/copy/migrate the current production data to
> the new servers? I am planning the following steps. Not sure if it is
> correct or not.
> >
> > 1. Stop the Postfix services on the old server and wait for few mins. So
> that no new emails will be coming to the old servers. Existing emails will
> be delivered to the receipients.
> >
> > 2. copy/migrate the data from old server to new servers. Please suggest
> what is the best way?
> >
> > 3. I see that dovecot version(2.0.9) in old production server, I do not
> know the which is the best option? see the options in the current version.
> >
> > =
> > [root@prodcution ~]# doveadm
> > usage: doveadm [-Dv] [-f ]  []
> >
> >  altmove [-u |-A] [-S ] 
> >  auth [-a ] [-x ]  []
> >  config [doveconf parameters]
> >  director add|flush|map|remove|status
> >  dump [-t ] 
> >  expunge [-u |-A] [-S ] 
> >  fetch [-u |-A] [-S ]  
> >  force-resync [-u |-A] [-S ] 
> >  help 
> >  import [-u |-A] [-S ]   parent mailbox> 
> >  kick [-a ] [-f] [|]
> >  log find|reopen|test
> >  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  penalty [-a ] []
> >  purge [-u |-A] [-S ]
> >  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  reload
> >  search [-u |-A] [-S ] 
> >  sis deduplicate|find
> >  stop
> >  user [-a ] [-x ]  [...]
> >
> > =
> >
> > Please suggest me.
> >
> > Thanks,
> > Kishore Potnuru
>
> `doveadm backup -R -u someone imapc:` comes to mind, with master
> password/master user authentication.
>
> Aki
>

Re: Migration from one server to 2 new servers

[Aki Tuomi]

> On 27/07/2020 11:59 Kishore Potnuru  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
> Postfix version - 2.6.6
> 
> 
> New Servers:
> ==
> Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> Dovecot version - 2.2.36 (1f10bfa63)
> Postfix version - 2.10.1 
> ==
> 
> What is the best way to stop/copy/migrate the current production data to the 
> new servers? I am planning the following steps. Not sure if it is correct or 
> not.
> 
> 1. Stop the Postfix services on the old server and wait for few mins. So that 
> no new emails will be coming to the old servers. Existing emails will be 
> delivered to the receipients.
> 
> 2. copy/migrate the data from old server to new servers. Please suggest what 
> is the best way?
> 
> 3. I see that dovecot version(2.0.9) in old production server, I do not know 
> the which is the best option? see the options in the current version.
> 
> =
> [root@prodcution ~]# doveadm
> usage: doveadm [-Dv] [-f ]  []
> 
>  altmove [-u |-A] [-S ] 
>  auth [-a ] [-x ]  []
>  config [doveconf parameters]
>  director add|flush|map|remove|status
>  dump [-t ] 
>  expunge [-u |-A] [-S ] 
>  fetch [-u |-A] [-S ]  
>  force-resync [-u |-A] [-S ] 
>  help 
>  import [-u |-A] [-S ]   mailbox> 
>  kick [-a ] [-f] [|]
>  log find|reopen|test
>  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>  penalty [-a ] []
>  purge [-u |-A] [-S ]
>  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>  reload
>  search [-u |-A] [-S ] 
>  sis deduplicate|find
>  stop
>  user [-a ] [-x ]  [...]
> 
> =
> 
> Please suggest me.
> 
> Thanks,
> Kishore Potnuru

`doveadm backup -R -u someone imapc:` comes to mind, with master 
password/master user authentication.

Aki

Re: Migration

[Alex La via dovecot]

Am 01.10.19 um 10:32 schrieb Sami Ketola via dovecot:
> 
> 
>> On 1 Oct 2019, at 11.29, Alex La via dovecot > > wrote:
>>
>> Am 30.12.18 um 10:53 schrieb Sami Ketola:
>>>
 On 29 Dec 2018, at 23.49, Hans Brage >>> > wrote:

 Hi!

 I'm currently running an small imap-server on Dovecot 2.2.4 but will retire
 that server. I've set up an new server with Dovecot 2.3.4 and will migrate
 the mailboxes (maildir-format) from the old to the new server. I'm planning
 to restructure the accounts a bit when migrating so I need to move them one
 by one. Its only a few so thats not a big issue.

 Both servers are using virtual accounts (users file).

 I've understood that best method for migration is to run doveadm backup -R
 from the new server. But I really cant figure out what other parameters or
 settings that I need to perform that task and if it should be run as user
 vmail or root.

 Would be greatful for any tips, hints, links or similiar.
>>>
>>>
>>> Once you have the new server set up, you can use dsync over ssh to sync the
>>> mailboxes with something like:
>>>
>>> doveadm backup -u user@newserver -R ssh sudouser@oldserver sudo
>>> /usr/bin/doveadm dsync-server -u user@oldserver
>>>
>>> needs to be run as root on new server. Also ssh access with keys and without
>>> password is recommended.
>>
>> I used to run `doveadm backup` on the new server with glusterfs and at the
>> middle of the sync the glusterfs is gone. Have anyone good experience with
>> glusterfs and `doveadm backup/sync`?
> 
> 
> No. I only have bad and very bad experiences with glusterfs in general. Too 
> many
> corruptions and unsync metadata (even with one node setup) that we migrated
> customer away from it and they are now using nfs instead.

Thank you for your fast answer. I had some issues with glusterfs in the
migration startup phase and wanted to know if this is only my experience or
someone else also.

We are now moving away from glusterfs and use dedicated storage.

> Sami

Regards
Alex

Re: Migration

[Sami Ketola via dovecot]

> On 1 Oct 2019, at 11.29, Alex La via dovecot  wrote:
> 
> Am 30.12.18 um 10:53 schrieb Sami Ketola:
>> 
>>> On 29 Dec 2018, at 23.49, Hans Brage  wrote:
>>> 
>>> Hi!
>>> 
>>> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire 
>>> that server. I've set up an new server with Dovecot 2.3.4 and will migrate 
>>> the mailboxes (maildir-format) from the old to the new server. I'm planning 
>>> to restructure the accounts a bit when migrating so I need to move them one 
>>> by one. Its only a few so thats not a big issue.
>>> 
>>> Both servers are using virtual accounts (users file).
>>> 
>>> I've understood that best method for migration is to run doveadm backup -R 
>>> from the new server. But I really cant figure out what other parameters or 
>>> settings that I need to perform that task and if it should be run as user 
>>> vmail or root.
>>> 
>>> Would be greatful for any tips, hints, links or similiar.
>> 
>> 
>> Once you have the new server set up, you can use dsync over ssh to sync the 
>> mailboxes with something like:
>> 
>> doveadm backup -u user@newserver -R ssh sudouser@oldserver sudo 
>> /usr/bin/doveadm dsync-server -u user@oldserver
>> 
>> needs to be run as root on new server. Also ssh access with keys and without 
>> password is recommended.
> 
> I used to run `doveadm backup` on the new server with glusterfs and at the
> middle of the sync the glusterfs is gone. Have anyone good experience with
> glusterfs and `doveadm backup/sync`?


No. I only have bad and very bad experiences with glusterfs in general. Too 
many corruptions and unsync metadata (even with one node setup) that we 
migrated customer away from it and they are now using nfs instead.

Sami

Re: Migration

[Tanstaafl]

On 12/31/2018, 5:22:48 AM, Ignacio García  wrote:
> A totally different approach (that is imap-server agnostic), providing 
> that you're setting up those new accounts with temporary passwords 
> (which you know), before users change their passwords to their liking: 
> you could also use imapsync ( https://github.com/imapsync/imapsync) . We 
> here use it with a batch file and a text file containing all accounts to 
> do mass-migrations, usually at night, when there's little to none user 
> interaction with their mail accounts. I like this approach because mail 
> service never gets interrupted and we do programmed syncs all night in 
> case DNS propagation takes more than expected and mail still arrives to 
> the old server.

Or, you can use Master Passwords on both sides, and just do the
migration at your leisure. I did this when migrating from our dovecot
server to Office 365.

Next time I'll look at using a dovecot method (DSync? doveadm?) but
still using Master Passwords.

Re: Migration

[Sami Ketola]

> On 31 Dec 2018, at 12.22, Ignacio García  wrote:
> 
> A totally different approach (that is imap-server agnostic), providing that 
> you're setting up those new accounts with temporary passwords (which you 
> know), before users change their passwords to their liking: you could also 
> use imapsync ( https://github.com/imapsync/imapsync) . We here use it with a 
> batch file and a text file containing all accounts to do mass-migrations, 
> usually at night, when there's little to none user interaction with their 
> mail accounts. I like this approach because mail service never gets 
> interrupted and we do programmed syncs all night in case DNS propagation 
> takes more than expected and mail still arrives to the old server.


I still don't recommend to use imapsync for migrations as UIDVALIDITY and UID 
numbers will change and end users will need to invalidate their local client 
caches and redownload all mail headers and usually also mail bodies again.

Sami

Re: Migration

[Ignacio García]

A totally different approach (that is imap-server agnostic), providing 
that you're setting up those new accounts with temporary passwords 
(which you know), before users change their passwords to their liking: 
you could also use imapsync ( https://github.com/imapsync/imapsync) . We 
here use it with a batch file and a text file containing all accounts to 
do mass-migrations, usually at night, when there's little to none user 
interaction with their mail accounts. I like this approach because mail 
service never gets interrupted and we do programmed syncs all night in 
case DNS propagation takes more than expected and mail still arrives to 
the old server.


Ignacio


El 30/12/2018 a las 23:09, Hans Brage escribió:

Thanks!

That was a really useful answer.

// Hans


Den 2018-12-30 kl. 10:53, skrev Sami Ketola:

On 29 Dec 2018, at 23.49, Hans Brage  wrote:

Hi!

I'm currently running an small imap-server on Dovecot 2.2.4 but will 
retire that server. I've set up an new server with Dovecot 2.3.4 and 
will migrate the mailboxes (maildir-format) from the old to the new 
server. I'm planning to restructure the accounts a bit when 
migrating so I need to move them one by one. Its only a few so thats 
not a big issue.


Both servers are using virtual accounts (users file).

I've understood that best method for migration is to run doveadm 
backup -R from the new server. But I really cant figure out what 
other parameters or settings that I need to perform that task and if 
it should be run as user vmail or root.


Would be greatful for any tips, hints, links or similiar.


Once you have the new server set up, you can use dsync over ssh to 
sync the mailboxes with something like:


doveadm backup -u user@newserver -R ssh sudouser@oldserver sudo 
/usr/bin/doveadm dsync-server -u user@oldserver


needs to be run as root on new server. Also ssh access with keys and 
without password is recommended.


Sami

Re: Migration

[Hans Brage]

Thanks!

That was a really useful answer.

// Hans


Den 2018-12-30 kl. 10:53, skrev Sami Ketola:

On 29 Dec 2018, at 23.49, Hans Brage  wrote:

Hi!

I'm currently running an small imap-server on Dovecot 2.2.4 but will retire 
that server. I've set up an new server with Dovecot 2.3.4 and will migrate the 
mailboxes (maildir-format) from the old to the new server. I'm planning to 
restructure the accounts a bit when migrating so I need to move them one by 
one. Its only a few so thats not a big issue.

Both servers are using virtual accounts (users file).

I've understood that best method for migration is to run doveadm backup -R from 
the new server. But I really cant figure out what other parameters or settings 
that I need to perform that task and if it should be run as user vmail or root.

Would be greatful for any tips, hints, links or similiar.


Once you have the new server set up, you can use dsync over ssh to sync the 
mailboxes with something like:

doveadm backup -u user@newserver -R ssh sudouser@oldserver sudo 
/usr/bin/doveadm dsync-server -u user@oldserver

needs to be run as root on new server. Also ssh access with keys and without 
password is recommended.

Sami

Re: Migration

[Sami Ketola]

> On 29 Dec 2018, at 23.49, Hans Brage  wrote:
> 
> Hi!
> 
> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire 
> that server. I've set up an new server with Dovecot 2.3.4 and will migrate 
> the mailboxes (maildir-format) from the old to the new server. I'm planning 
> to restructure the accounts a bit when migrating so I need to move them one 
> by one. Its only a few so thats not a big issue.
> 
> Both servers are using virtual accounts (users file).
> 
> I've understood that best method for migration is to run doveadm backup -R 
> from the new server. But I really cant figure out what other parameters or 
> settings that I need to perform that task and if it should be run as user 
> vmail or root.
> 
> Would be greatful for any tips, hints, links or similiar.


Once you have the new server set up, you can use dsync over ssh to sync the 
mailboxes with something like:

doveadm backup -u user@newserver -R ssh sudouser@oldserver sudo 
/usr/bin/doveadm dsync-server -u user@oldserver

needs to be run as root on new server. Also ssh access with keys and without 
password is recommended.

Sami

Re: Migration

[Benny Pedersen via dovecot]

Hans Brage skrev den 2018-12-29 22:49:


Would be greatful for any tips, hints, links or similiar.


if you want external tools i think imapsync is best way to sync all, it 
can keep source or delete, so you have backup in case of errors, it does 
not sync sieve, this is still not makeed, so each user must self copy 
sieve scripts from old to new via webmail or thunderbird with sieve 
plugin

Re: migration from zimbra to dovecot

[Sami Ketola]

> On 21 Oct 2015, at 20:13, micah  wrote:
> Are there any migration scripts to handle UID conversion for moving from
> a zimbra setup to dovecot? It would be nice to move all the mail without
> having re-download it all!

Depends on what is the imap backend behind Zimbra or if using Zimbra builtin 
imap backend,
but usually UID:s are preserved when mails are migrated by using dsync over 
imapc connection
when the dsync target platform is Dovecot. This however requires that master 
password can be 
set on Zimbra side or users passwords are known.

Sami

Re: Migration from courier-imap to dovecot

[Pascal Volk]

On 06/23/2015 02:57 PM, alex wrote:
 hello,
 
 I search a solution to migrate a courier-impa mail accounts in maildir 
 format to a dovecot mail accounts in sandbox format.
 The first server is an ubuntu 10.4 with courier-imap in maildir format, 
 the accounts are managed by postfix 2.7.0 with MySQL
 The second server is an debian 7.8 (wheezy) with dovecot 2.2.13 in sdbox 
 format, the accounts are managed by postfix 2.9.6 with MySQL
 
 My request is, how to import and convert the mail accounts ??


Did you read http://wiki2.dovecot.org/Migration/Courier?


Regards,
Pascal
-- 
The trapper recommends today: c01dcofe.1517...@localdomain.org

Re: migration from cyrus with dsync sieve problem

[Jogi Hofmüller]

Hi Alessandro,

Am 2014-09-15 um 16:07 schrieb Alessandro Bono:

 i'm migrating a cyrus imapd server to dovecot with dsync
 everyting seems working but sieve rules are not copied to dovecot server
 I searched for documentation but without any luck
 I use the configuration below with

We are in the process of doing the same here.  After first trials with
dsync we went to migrating with cyrus2dovecot.  For migrating sieve
scripts we wrote a simple shell script.

The main reason why we abandoned dsync is that it was just painfully
slow.  I don't remember if it did (attempt) to syn sieve scripts.

One thing that we still could not solve is that when migrating shared
folders, all flags for all mail are set to unread.  Would be interesting
if you use shared mailboxes and how you tackle this topic.

Cheers,
-- 
J.Hofmüller

Im Übrigen bin ich der Meinung, das Joanneum muss zerschlagen werden! -
Barbara Fischer



signature.asc
Description: OpenPGP digital signature

Re: migration from cyrus with dsync sieve problem

[Alessandro Bono]

Hi Jogi

Il 18/09/14 14:08, Jogi Hofmüller ha scritto:

Hi Alessandro,

Am 2014-09-15 um 16:07 schrieb Alessandro Bono:


i'm migrating a cyrus imapd server to dovecot with dsync
everyting seems working but sieve rules are not copied to dovecot server
I searched for documentation but without any luck
I use the configuration below with

We are in the process of doing the same here.  After first trials with
dsync we went to migrating with cyrus2dovecot.  For migrating sieve
scripts we wrote a simple shell script.

The main reason why we abandoned dsync is that it was just painfully
slow.  I don't remember if it did (attempt) to syn sieve scripts.

One thing that we still could not solve is that when migrating shared
folders, all flags for all mail are set to unread.  Would be interesting
if you use shared mailboxes and how you tackle this topic.
I can confirm that dsync not sync sieve script, I finished migration and 
recreate sieve rules by hand  (and yes dsync it's really slow)
but a new problem appears, dovecot not support duplication suppression, 
I partially solved with postfix parameter enable_original_recipient = 
no but it's not a complete solution
I have to migrate another system with shared mailboxes but I still have 
to configure the new server



Cheers,


--
Cordiali saluti

Alessandro Bono

[Dovecot] Filesystems (was Re: Migration questions...)

[Seth Mattinen]

Richard Hobbs wrote:

 Trouble is... i've been googling this as well, just now, and loads of
 people say XFS has the better performance, but loads of other people say
 ReiserFS has the better performance.

It starts to become a religious argument at some point.


 We have battery backed up RAID controllers too, in this new system, and
 the systems are UPSd, so on that basis i'm still none the wiser! lol

 I appreciate your experience with XFS is a positive one, but even the
 dovecot web site says XFS might now be a good choice...

 http://wiki.dovecot.org/MailboxFormat/Maildir

 What a tough decision! I know it probably won't make too much difference
 in my situation, but i want this to be a very long-term solution, so
 want to do it right first time!

 Any other opinions on XFS vs Reiserfs with Dovecot maildir?

 Thanks again!

 Richard.



If you have time to play tweak the filesystem:

http://everything2.com/index.pl?node_id=1479435

It's a good comparison of etx3, xfs, and reiser from a performance
standpoint. Also try this if you want to pull the plug or randomly
reboot and see what happens:

http://brad.livejournal.com/2116715.html

~Seth