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 message..
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 d
• 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 descri
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
Il giorno mer 10 apr 2024 alle ore 22:32 Marc via dovecot
ha scritto:
> 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 standards are having yearly
> innovations. Or is this a service you provide for clients?
In my
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, thi
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 you
>
>
>
> • 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 s
>
> 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 fro
• 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 important)
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 h
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 member
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 BLF-CRYPT
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:
https://kaworu.ch/blog/2016/04/20/strong-crypt-schem
I've asked this before, but now it's time to move one server to
another, I can't delay the operation anymore (the older server is
failing)
Both server are pretty old: 1.2.15
Probably, faster way would be to rsync all mailboxes from the older
server to the newer one. I can start migrating ever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 24 Nov 2017, Gandalf Corvotempesta wrote:
I've asked this before, but now it's time to move one server to
another, I can't delay the operation anymore (the older server is
failing)
Both server are pretty old: 1.2.15
Probably, faster way wo
Don't lose any of the dovecot-* files and your clients should be fine. I've
done 1) a couple of times and nobody got hurt.What you should do is keep the
two servers (the old and the new one), and once the new one is ready test with
your client only (change your client's IMAP/POP server settings)
> On 1 Nov 2016, at 14.10, Tanstaafl wrote:
>
> On 11/1/2016 3:58 AM, Sami Ketola wrote:
>> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>>> Ok, interesting. So... how does dsync do it? Or would it only work
>>> between two dovecot servers?
>>>
>>> I'm interested in migrating from other servers
On 11/1/2016 3:58 AM, Sami Ketola wrote:
> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>> Ok, interesting. So... how does dsync do it? Or would it only work
>> between two dovecot servers?
>>
>> I'm interested in migrating from other servers (Office 365 in one case).
> Dsync does not use IMAP pro
> On 31 Oct 2016, at 13.11, Tanstaafl wrote:
>
> On 10/30/2016 5:32 AM, Sami Ketola wrote:
>> On 28 Oct 2016, at 16.54, Tanstaafl wrote:
>>> Oh... I thought the --useuid option eliminated this problem?
>>>
>>> https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
>
>> It does not. There is
On 10/30/2016 5:32 AM, Sami Ketola wrote:
> On 28 Oct 2016, at 16.54, Tanstaafl wrote:
>> Oh... I thought the --useuid option eliminated this problem?
>>
>> https://imapsync.lamiral.info/FAQ.d/FAQ.Duplicates.txt
> It does not. There is no option at IMAP level to set the UID.
>
> In this case —u
> On 28 Oct 2016, at 16.54, Tanstaafl wrote:
>
> On 10/27/2016 8:36 AM, Timo Sirainen wrote:
>> On 27 Oct 2016, at 15:29, Tanstaafl wrote:
>>> On 10/26/2016 2:38 AM, Gandalf Corvotempesta
my only question is: how to manage the email received on the new server
during the last rsync ph
On 10/27/2016 8:36 AM, Timo Sirainen wrote:
> On 27 Oct 2016, at 15:29, Tanstaafl wrote:
>> On 10/26/2016 2:38 AM, Gandalf Corvotempesta
>>> my only question is: how to manage the email received on the new server
>>> during the last rsync phase?
>>
>> Use IMAPSync - much better than rsync for thi
On 27 Oct 2016, at 15:58, Gandalf Corvotempesta
wrote:
>
> 2016-10-27 14:36 GMT+02:00 Timo Sirainen :
>> imapsync will change IMAP UIDs and cause clients to redownload all mails.
>> http://wiki2.dovecot.org/Migration/Dsync should work though.
>
> Just to be sure: dsync from the *new* node woul
2016-10-27 14:36 GMT+02:00 Timo Sirainen :
> imapsync will change IMAP UIDs and cause clients to redownload all mails.
> http://wiki2.dovecot.org/Migration/Dsync should work though.
Just to be sure: dsync from the *new* node would connect via IMAP to
the older node and transfer everything ?
By ru
On 27 Oct 2016, at 15:29, Tanstaafl wrote:
>
> On 10/26/2016 2:38 AM, Gandalf Corvotempesta
> wrote:
>> This is much easier than dovecot replication as i can start immedialy with
>> no need to upgrade the old server
>>
>> my only question is: how to manage the email received on the new server
>
On 10/26/2016 2:38 AM, Gandalf Corvotempesta
wrote:
> This is much easier than dovecot replication as i can start immedialy with
> no need to upgrade the old server
>
> my only question is: how to manage the email received on the new server
> during the last rsync phase?
Use IMAPSync - much bett
2016-10-26 8:57 GMT+02:00 Aki Tuomi :
> If you are moving from 1.x to 2.x, I think you should make some trials
> first, and preferably move the user one at a time, blocking access to
> old server/new server during move. It is very forklift upgrade, much danger.
Yes, I'll do some test migration bef
On 26.10.2016 09:38, Gandalf Corvotempesta wrote:
> Il 26 ott 2016 8:30 AM, "Aki Tuomi" ha scritto:
>> I would recommend using same major release with replication.
>>
>> If you are using maildir++ format, it should be enough to copy all the
>> maildir files over and start dovecot on new server.
Il 26 ott 2016 8:30 AM, "Aki Tuomi" ha scritto:
> I would recommend using same major release with replication.
>
> If you are using maildir++ format, it should be enough to copy all the
> maildir files over and start dovecot on new server.
>
This is much easier than dovecot replication as i can s
On 26.10.2016 09:27, Gandalf Corvotempesta wrote:
> Il 24 ott 2016 5:11 PM, "Michael Seevogel" ha scritto:
>> I meant your old server. With "old" I was expecting something like Debian
> Sarge or SuSE Linux 9.3. That would have been really old, but since you are
> on Debian Squeeze, I would defin
Il 24 ott 2016 5:11 PM, "Michael Seevogel" ha scritto:
> I meant your old server. With "old" I was expecting something like Debian
Sarge or SuSE Linux 9.3. That would have been really old, but since you are
on Debian Squeeze, I would definitely choose the way with an upgraded
Dovecot version and i
Am 24.10.2016 um 15:25 schrieb Gandalf Corvotempesta:
2016-10-24 14:47 GMT+02:00 Michael Seevogel :
If your server OS supports newer Dovecot versions then I would highly
suggest you to upgrade to Dovecot 2.2.xx (or at least to the latest 2.1) and
set up Dovecot's replication[1] feature.
Are yo
2016-10-24 14:47 GMT+02:00 Michael Seevogel :
> P.S. You should think about to use on the new server mdbox as mailbox
> format.
> That's kinda a hybrid of mbox and maildir and benefits of features of both
> its predecessors. However, backup and restoring is in case of mdbox "a bit"
> different. Jus
2016-10-24 14:47 GMT+02:00 Michael Seevogel :
> If your server OS supports newer Dovecot versions then I would highly
> suggest you to upgrade to Dovecot 2.2.xx (or at least to the latest 2.1) and
> set up Dovecot's replication[1] feature.
Are you talking about the new server or the older one that
2016-10-24 11:23 GMT+02:00 Karol Augustin :
> When I am doing this I just turn off both servers for the third sync.
> Its short enough to not cause much problem. And then after third sync I
> start the new server and all clients can connect to it so I also
> mitigate any problems resulting from cli
Am 24.10.2016 um 09:00 schrieb Gandalf Corvotempesta:
Hi
i have to migrate, online, a dovecot 1.2.15 to a new server. Which is the
best way to accomplish this?
I have 2 possibility:
1) migrate from the very old server to a newer server with the same dovecot
version
2) migrate from the very old s
On 2016-10-24 8:00, Gandalf Corvotempesta wrote:
> can i simply use rsync to sync everything and, when the sync is quick, move
> the mailbox from the old server to the new server? My biggest concern is
> how to manage the the emails that are coming during the server switch.
>
> Let's assume a 50g
On 2013-12-27 9:33 AM, Charles Marcus wrote:
Damn! How did I miss that. The 'T' is for 'trashed', so of course,
when the Inbox is expunged, they will be deleted...
Thanks Rick, for the gentle clue stick...
Apologies to all for the noise.
--
Best regards,
*/Charles/*
40 matches
Mail list logo
