in my case, 99% of mailboxes are imap
Il gio 11 apr 2024, 00:08 Michael Peddemors via dovecot
ha scritto:
Of course, anyone who is stilling using POP (Leave on Server)
presents a
different challenge.. Depending on the client, and how the client
treated the UID of the
Of course, anyone who is stilling using POP (Leave on Server) presents a
different challenge.. Depending on the client, and how the client
treated the UID of the message..
The rest should present no issue..
On 2024-04-10 14:25, Kirill Miazine via dovecot wrote:
• Gandalf Corvotempesta via
• Gandalf Corvotempesta via dovecot [2024-04-10 23:18]:
Il giorno mer 10 apr 2024 alle ore 23:12 Kirill Miazine via dovecot
ha scritto:
UIDVALIDITY change
In which case uidvalidity would change ?
if you do rsync, it doesn't. UIDVALIDITY is stored in dovecot-uidlist in
maildirs, as
Il giorno mer 10 apr 2024 alle ore 23:12 Kirill Miazine via dovecot
ha scritto:
> UIDVALIDITY change
In which case uidvalidity would change ?
Manually changes in config file ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email
• Gandalf Corvotempesta via dovecot [2024-04-10 22:59]:
What could trigger a new re-download of message ?
UIDVALIDITY change
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
r clients?
In my case the server migration has to be done because the old
datacenter is closing and i have to move all datas to a new server on
a different location.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Il giorno mer 10 apr 2024 alle ore 21:40 Kirill Miazine via dovecot
ha scritto:
> What you describe is exactly what I have been doing since ... forever
>
> - reduce TTL
> - setup new server
> - rsync
> - stop ALL mail services on old server (also anything which might be
> doing deliveries,
Can you expand and explain this:
Why? The whole idea about having a LTS distribution is that you almost never
need to do this?
Can you provide a link for context?
On 4/10/2024 3:25 PM, Marc via dovecot wrote:
• Gandalf Corvotempesta via dovecot [2024-04-10 21:07]:
Guys, any help?
What
>
>
>
> • Gandalf Corvotempesta via dovecot [2024-04-10 21:07]:
> > Guys, any help?
>
> What you describe is exactly what I have been doing since ... forever
>
Why? The whole idea about having a LTS distribution is that you almost never
need to do this? It is not like the imap/pop/smtp
>
> Guys, any help?
this lacks context.
> Also, what would happen if the new server has a different hostname ?
So put temporary haproxy infront of it?
> Il giorno dom 10 mar 2024 alle ore 14:28 Gandalf Corvotempesta
> ha scritto:
> >
> > Hi guys
> > I have to migrate around 10k mailboxes
• Gandalf Corvotempesta via dovecot [2024-04-10 21:07]:
Guys, any help?
What you describe is exactly what I have been doing since ... forever
- reduce TTL
- setup new server
- rsync
- stop ALL mail services on old server (also anything which might be
doing deliveries, this is
Guys, any help?
Also, what would happen if the new server has a different hostname ?
Il giorno dom 10 mar 2024 alle ore 14:28 Gandalf Corvotempesta
ha scritto:
>
> Hi guys
> I have to migrate around 10k mailboxes from dovecot 2.13 to (i think)
> the same version but on a different server.
>
> I
On 05/04/2024 17:49 EEST Marc via dovecot
wrote:
doveadm sync -u testacc
'mdbox:/home/testing/testacc/mdbox:INDEX=/home/testing/
testacc/index:CONT
ROL=/home/testing/testacc/mail/control:LAYOUT=index'
>
> >
> > doveadm sync -u testacc
> 'mdbox:/home/testing/testacc/mdbox:INDEX=/home/testing/testacc/index:CONT
> ROL=/home/testing/testacc/mail/control:LAYOUT=index'
> >
> > Which gives me the expectec result. But I have also an archive
> namespace and an alt namespace that is going to be quite a lot
Like eg reindex or so? I always had the impression
> > this
> > > > affects how messages are stored.
> > > > >
> > > > > mail_location = mdbox:xx:INDEX=xx:CONTROL=/xxx
> > > > > becomes:
> > > > > mail_location =
>
; So you can just add this to an existing configuration, without the
> need
> > > to do anything? Like eg reindex or so? I always had the impression
> this
> > > affects how messages are stored.
> > > >
> > > > mail_location = mdbox:xx:INDEX=xx:CONTROL
xisting configuration, without the need
> > to do anything? Like eg reindex or so? I always had the impression this
> > affects how messages are stored.
> > >
> > > mail_location = mdbox:xx:INDEX=xx:CONTROL=/xxx
> > > becomes:
> > > mail_lo
t; > mail_location = mdbox:xx:INDEX=xx:CONTROL=/xxx
> > becomes:
> > mail_location = mdbox:xx:INDEX=xx:CONTROL=/xxx:LAYOUT:index
> >
> > Does this really speed things up?
> >
>
> You can't put it on existing setup just like that, you need
Should work then if you have roundcube 1.6.x and php8.2 which is also
the
bookworm package version.
Depends on your server spec / number of users if you use argon2 over
bcrypt.
One approach might be to just migrate all users to BLF-CRYPT anyway, and
then
set the recommended dovecot
Hello,
Thanks. The other utility I would be using is the Roundcube webmail
password plugin. Still trying to figure the best option.
More opinions?
Thanks.
Dave.
On 6/24/23, Robert Lister wrote:
>
> I did a similar upgrade, and now in the process of migrating from
> SHA512-CRYPT
> to
I did a similar upgrade, and now in the process of migrating from
SHA512-CRYPT
to BLF-CRYPT with an appropriately set rounds, as I think the default
rounds
is a little low.
A good write-up on migrating passwords and calculating the rounds:
Hello,
I'm migrating to a new server. It's running Debian 11 currently though
that's going 12 this weekend. Currently it uses Openssl v3.0.9, and
dovecot 2.3.13 and MySQL (in this case Mariadb) for storing user
account information v10.6.14. My question is in regards password
storage and
2023 at 3:26 PM aki.tuomi via dovecot
> > mailto:dovecot@dovecot.org>> wrote:
> >
> > Please see https://doc.dovecot.org/admin_manual/migrating_mailboxes/
> > <https://doc.dovecot.org/admin_manual/migrating_mailboxes/>
> >
> > Aki
> >
&g
ail 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 me
Original message
From: tseeger...@gmail.com <mailto:tseeger...@gmail.com>
Date: 6/8/23 16:10 (GMT+02:00)
To: dovecot@dovecot.org <mailto:dovecot@dovecot.org>
Subject: Migration dovecot server with local users to dovecot with
virtual mailboxes
Hello,
..@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
> 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,
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
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
https://pastebin.com/rDSeBcLe
My migration I made using: 1. Edit dovecot.conf with new mdbox and
adding separator 2. dsync mirror per user with old maildir:~/mail 3.
missing mailboxes: tried with doveadm sync also with -f mode and
specified mailboxes. No luck.
dsync -v -u ad...@sajdowski.de m
On 11/17/22 09:28, Oscar del Rio wrote:
I believe there is no Dovecot APT repo for Ubuntu 22 (yet)
https://repo.dovecot.org/
Very true. I believe I read somewhere that there will not be a Dovecot
2.3 repo for jammy, but there will be one for 2.4 when it is released.
Thanks,
Shawn
On 2022-11-17 10:26 a.m., Shawn Heisey wrote:
On 11/15/22 03:29, Markus Wienhöfer wrote:
we are currently using Dovecot 2.2 (from the Ubuntu 18.04 repos) and
would like to migrate to 2.3
I have read the migration documentation regarding the configuration
changes. Apart from
On 11/15/22 03:29, Markus Wienhöfer wrote:
we are currently using Dovecot 2.2 (from the Ubuntu 18.04 repos) and
would like to migrate to 2.3
I have read the migration documentation regarding the configuration
changes. Apart from that, is it feasible/possible to change from
Ubuntu to official
Hi,
we are currently using Dovecot 2.2 (from the Ubuntu 18.04 repos) and would like
to migrate to 2.3
I have read the migration documentation regarding the configuration changes.
Apart from that, is it feasible/possible to change from Ubuntu to official
Dovecot repositories and upgrade
> These links:
>
> http://dag.wieers.com/rpm/packages/pine/pine-4.64-3.el4.rf.i386.rpm
> http://staff.washington.edu/chappa/pine/info/maildir.html
>
> on this page
>
> https://wiki.dovecot.org/Migration/MailFormat
>
> at the Dovecot wiki do not lead to usefu
Hi,
These links:
http://dag.wieers.com/rpm/packages/pine/pine-4.64-3.el4.rf.i386.rpm
http://staff.washington.edu/chappa/pine/info/maildir.html
on this page
https://wiki.dovecot.org/Migration/MailFormat
at the Dovecot wiki do not lead to useful results.
The dag.wieers.com link seems
https://wiki.dovecot.org/Migration/MailFormat
If you have not yet, please read this. Conversion can be done in-place.
While doing the in-place migration, I would strongly suggest keeping the users
out from the server. While it's possible to do while there are users actively
using the server
are rather large
-- 100's of MB (one of the reasons for migrating).
What I have tried has not worked for me. Below, I describe what I tried, how I
tested before I tried, what went wrong, and the current setup (pre-migration).
What I tried:
=
stop exim4
service dovecot stop
Make dovecot
meter in the mail location specification. If the INDEX parameter is
specified, it will override the root mail location for index files and
the "map index" file (mdbox only). "/
Even with this warning I performed the migration of some accounts as a test.
running the commands from
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
> 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 th
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
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
o 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
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
> rep
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
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
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).
Our migration command
doveadm -o mail_fsync=never
> 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
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
: 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.
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
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 g
=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
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
rom: 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 m
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
perations,
> because Dovecot needs to stat() every file in a directory to gather
> those information.
i've initially avoided sdbox, assuming the index-file dependency to be an
additional failure pt,
but that^^ is somewhat compelling.
i'd like to migrate maildir -> sdbox.
t
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
? 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 migrat
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 =
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
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:
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"
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
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 |
Hi All,
I have tried the below command to migrate the data from the old
server(dovecot version: 2.0.9) to new servers(dovecot version: 2.2.36
(1f10bfa63)). But it's throwing an error.
old server name: production1
new server1 name: production2 (for HA/Replication)
new server2 name: production3
Am 30.07.20 um 23:02 schrieb Ralf Becker:
> Do both replication nodes need to be updated at the same time?
>
> Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)?
>
> Ralf
In case someone's looking here for an answer about 2.2 to 2.3 update
with replication and directors:
1. I first updated
Do both replication nodes need to be updated at the same time?
Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)?
Ralf
--
Ralf Becker
EGroupware GmbH [www.egroupware.org]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern,
_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?
>>
>> M
ase 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 on
uing 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
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
}
>
> 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 Kis
e 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
&
= /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 wr
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
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
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.
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
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
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
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
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
> 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
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
> 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
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 ]
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.
> 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.
>
>
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
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
> 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”.
> 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
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
> 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.
>
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:
gin forwarded message:
>
> From: Antonio Leding
> Subject: Dsync mail migration from v2.2 --> v2.3
> Date: July 13, 2020 at 8:45:18 PM PDT
> To: dovecot@dovecot.org
>
> Hello all,
>
> I’ve been battling how to migrate my imap mail following a new server install
> t
.
Questions
First and foremost — any obvious issues here?
Next, any advice and\or lessons learned with this type of migration?
Finally, presuming this is the proper way to do this, will this migrate all
mail content including Sent, Deleted, Drafts, etc.?
Thanks in advance for taking the tim
On 2020-03-28 23:54, Stefano Antonelli wrote:
I've attached my script in case it's helpful to anyone in a similar
situation. It took quite a bit of effort to get this right, highly
depends on the format of the original mailstore, and I've only tested
this on one smaller mailbox (<400 messages).
1 - 100 of 952 matches
Mail list logo
