Hello to everyone!
Ooops, we are using SIS, guess the solution for a similar optimization will be a native deduplicated filesystem.
For server synchronization (non "realtime") we are using "imapsync" ( https://imapsync.lamiral.info/ )
regards!
On 16/10/23 08:11, Taavi Ansper via dovecot wrote:
Hi
So in my 99-dsync.conf
This would not work in newer releases?
service replicator { unix_listener replicator-doveadm { mode = 0666 } }
plugin { mail_replica = tcp:example.com:12345 }
If that is the case, well then I have to find another way to keep mails in sync between 2 mailservers. Hope the community will find a new solution!
On 16.10.23 09:30, Michael Slusarz via dovecot wrote:
Aki is correct and is consistent with what I said in the video, although I could have phrased my explanation better. "dsync" refers to the tool/utility (part of doveadm) that does mail synchronization between a source account to a destination account. As Aki said, this is not going anywhere. This is a necessary tool for any kind of migrations, for example. dsync is under active maintenance, as we heavily use this tool internally. What is being removed is the replicator plugin (that used dsync). That's what is being referred to in the video. Replicator hasn't been actively maintained for years now so this was dead code anyway. To answer the OP: sis is also being removed and should not be used by any new installation. Code remains to read data written by the old plug-in so that these installations don't require a migration between 2.3 and 2.4. This is another plugin that hasn't be actively maintained in years, and has all kinds of limitations that prevent it from running at scale. Neither replicator nor sis is code that is moving from open to closed source. These plugins aren't used in Pro. They are unmaintained so they are being removed, as happens with any kind of old code. michael
On 10/13/2023 1:26 PM MDT Laura Smith via dovecot <dovecot@dovecot.org> wrote:
FUD ?
I knew someone would accuse me of that which is why I linked to the video from the horse's mouth, I transcribe what the speaker said:
"there will be an open source version, but that open source version will be maintained for single server use only. we are actually taking out anything any actually kinda' involves multiple servers, dsync replication and err some other stuff. so dovecot will be a fully-featured single node server"
------- Original Message ------- On Friday, October 13th, 2023 at 19:37, Aki Tuomi <aki.tuomi@open-xchange.com> wrote:
Dear Laura, please don't spread FUD that you made up.
Dsync is not going anywhere, and we are not close-sourcing Dovecot Core. There is not a trove of code going into Dovecot 3.0 that "never sees the daylight".
Thank you, Aki
On 13/10/2023 21:10 EEST Laura Smith via dovecot dovecot@dovecot.org wrote:
TL;DR If you are a Dovecot Community user, don't waste your time reading the Dovecot Pro release notes.
To expand:
I think you have to understand that lots of things that are going into Dovecot 3 (Pro) will never see the light of day in the community edition.
In addition, Dovecot have publicly quite plainly announced in public that they are actively removing all multi-server related functionality from Dovecot Community.
I don't think the community has quite yet grasped it. Things like dsync will be GONE in the community version.
If you don't believe me, look at this video, about 15 minutes in: https://youtu.be/s-JYrjCKshA?feature=shared&t=912
------- Original Message ------- On Friday, October 13th, 2023 at 17:15, Sebastian Marsching sebastian@marsching.com wrote:
Hi,
I am currently in the process of planning a new deployment of Dovecot. I was planning to use mdbox or sdbox with “mail_attachment_fs = sis posix”, but I stumbled across the following notice in the documentation for Dovecot 3.0
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Com os melhores cumprimentos, <https://www.ipl.pt/> Pedro Ribeiro *Departamento de Sistemas de Informação e Comunicações - IPLNet <https://www.net.ipl.pt>* Serviços da Presidência Telf. +351 210 464 700 / Ext. 80101
Hello to everyone! Ooops, we are using SIS, guess the solution for a similar optimization will be a native deduplicated filesystem. For server synchronization (non "realtime") we are using "imapsync" ( https:// imapsync.lamiral.info/ ) regards! On 16/10/23 08:11, Taavi Ansper via dovecot wrote: Hi
So in my 99-dsync.conf
This would not work in newer releases?
service replicator {
unix_listener replicator-doveadm {
mode = 0666
}
}
plugin {
mail_replica = tcp:example.com:12345
}
If that is the case, well then I have to find another way to keep
mails in sync between 2 mailservers. Hope the community will find a
new solution!
On 16.10.23 09:30, Michael Slusarz via dovecot wrote:
Aki is correct and is consistent with what I said in the
video, although I could have phrased my explanation better.
"dsync" refers to the tool/utility (part of doveadm) that
does mail synchronization between a source account to a
destination account. As Aki said, this is not going
anywhere. This is a necessary tool for any kind of
migrations, for example. dsync is under active
maintenance, as we heavily use this tool internally.
What is being removed is the replicator plugin (that used
dsync). That's what is being referred to in the video.
Replicator hasn't been actively maintained for years now so
this was dead code anyway.
To answer the OP: sis is also being removed and should
not be used by any new installation. Code remains to read
data written by the old plug-in so that these installations
don't require a migration between 2.3 and 2.4. This is
another plugin that hasn't be actively maintained in years,
and has all kinds of limitations that prevent it from
running at scale.
Neither replicator nor sis is code that is moving from
open to closed source. These plugins aren't used in Pro.
They are unmaintained so they are being removed, as happens
with any kind of old code.
michael
On 10/13/2023 1:26 PM MDT Laura Smith via dovecot
<dovecot@dovecot.org> wrote:
FUD ?
I knew someone would accuse me of that which is
why I linked to the video from the horse's mouth,
I transcribe what the speaker said:
"there will be an open source version, but that
open source version will be maintained for single
server use only. we are actually taking out
anything any actually kinda' involves multiple
servers, dsync replication and err some other
stuff. so dovecot will be a fully-featured single
node server"
------- Original Message -------
On Friday, October 13th, 2023 at 19:37, Aki Tuomi
<aki.tuomi@open-xchange.com> wrote:
Dear Laura, please don't spread FUD
that you made up.
Dsync is not going anywhere, and we are
not close-sourcing Dovecot Core. There
is not a trove of code going into
Dovecot 3.0 that "never sees the
daylight".
Thank you,
Aki
On 13/10/2023 21:10 EEST
Laura Smith via dovecot
dovecot@dovecot.org wrote:
TL;DR If you are a Dovecot
Community user, don't waste
your time reading the Dovecot
Pro release notes.
To expand:
I think you have to
understand that lots of
things that are going into
Dovecot 3 (Pro) will never
see the light of day in the
community edition.
In addition, Dovecot have
publicly quite plainly
announced in public that they
are actively removing all
multi-server related
functionality from Dovecot
Community.
I don't think the community
has quite yet grasped it.
Things like dsync will be
GONE in the community
version.
If you don't believe me, look
at this video, about 15
minutes in:
https://youtu.be/s-
JYrjCKshA?feature=shared&t=912
------- Original Message ----
---
On Friday, October 13th, 2023
at 17:15, Sebastian Marsching
sebastian@marsching.com
wrote:
Hi,
I am currently in
the process of
planning a new
deployment of
Dovecot. I was
planning to use
mdbox or sdbox with
“mail_attachment_fs
= sis posix”, but I
stumbled across the
following notice in
the documentation
for Dovecot 3.0
_______________________________________________
dovecot mailing
list -
-
dovecot@dovecot.org
To unsubscribe send
an email to
dovecot-
leave@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-
leave@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-leave@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-leave@dovecot.org-- Com os melhores cumprimentos, [https://www.net.ipl.pt/ipl_img/logo_ipl_email.png] Pedro Ribeiro Departamento_de_Sistemas_de_Informação_e_Comunicações_-_IPLNet Serviços da Presidência Telf. +351 210 464 700 / Ext. 80101