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

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,

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

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 >

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

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

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

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

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

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

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

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

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

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

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

> 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

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

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

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

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

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

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.

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

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

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

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

Re: migration from 2.0.16

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

RE: migration from 2.0.16

> 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

Re: migration from 2.0.16

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

Re: migration from 2.0.16

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

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

RE: migration from 2.0.16

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

RE: migration from 2.0.16

=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

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

RE: migration from 2.0.16

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,

Re: Migration issue

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

Re: Migration issue

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

Re: Migration issue

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

Re: Migration issue

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

Re: Migration issue

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:

Re: Migration issue

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"

Re: Migration issue

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

Re: Migration issue

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 |

Re: Migration issue

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

Re: Migration issue

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 =

Re: Migration issue

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

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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args =

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side. Do you have dsync on the 2.0.9 machine? > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru > wrote: > > This is what my

Re: Migration from one server to 2 new servers

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.

Re: Migration from one server to 2 new servers

Well that option set still doesn’t look correct… Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36… [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say “production1”…I just double-checked as well... FWIW…the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned

Re: Migration from one server to 2 new servers

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

> 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

Re: Migration from one server to 2 new servers

Yes. Please find the details of the servers below. I am executing the command from one of the new servers. My Current Production Server details: Linux OS- Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6

Re: Migration from one server to 2 new servers

> 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

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 ]

Re: Migration from one server to 2 new servers

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.

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

> 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

Re: Migration from one server to 2 new servers

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

Re: Migration from one server to 2 new servers

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

Re: Migration

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!

Re: Migration

> 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

Re: Migration

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

Re: Migration

> 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

Re: Migration

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

Re: Migration

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

Re: Migration

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

Re: Migration

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

Re: migration from zimbra to dovecot

> 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

Re: Migration from courier-imap to dovecot

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

Re: migration from cyrus with dsync sieve problem

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

Re: migration from cyrus with dsync sieve problem

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

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

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