Re: The end of Dovecot Director?
You still need in some sense one coherent file system to store and retrieve the mail messages. Although a load-balance cluster would still be quite useful for rejecting the bulk of unauthorized connections. I am sure in many cases a small/medium server can in fact sit and function quite adequately behind a large enterprise load balancing firewall and proxy, given the typical quantities of spam "out there" and the large number of bad connections typically attempted on any given system. On Thursday, October 20, 2022 9:19:59 PM AKDT, Zhang Huangbin wrote: On Oct 21, 2022, at 4:19 AM, Antonio Leding wrote: My understanding is that Director is targeted toward large enterprise mail installations that will incorporate several servers for a given function. In such an environment, Director would be the fore-person\traffic-cop keeping things organized & squared-away. Director is used when you setup frontend servers in a load-balance cluster, proxy imap/pop3/lmtp/managesieve requests to backend Dovecot servers. I setup load-balance cluster for clients with HAProxy + KeepAlived + Dovecot Director running in frontend servers, so sad we have to find an alternative to replace Director in such case. It's not about "small/medium" servers, but the demand of imap/pop3/lmtp proxy service, especially in load-balance cluster. Zhang Huangbin, founder of: - iRedMail: Open source email server solution: https://www.iredmail.org/ - Spider: Lightweight, on-premises Email Archiving Software: https://spiderd.io
Re: The end of Dovecot Director?
Please post your solution. Sent from my iPhone - please excuse brevity and typos > On Oct 20, 2022, at 10:21 PM, Zhang Huangbin wrote: > > > >> On Oct 21, 2022, at 4:19 AM, Antonio Leding wrote: >> >> My understanding is that Director is targeted toward large enterprise mail >> installations that will incorporate several servers for a given function. In >> such an environment, Director would be the fore-person\traffic-cop keeping >> things organized & squared-away. > > Director is used when you setup frontend servers in a load-balance cluster, > proxy imap/pop3/lmtp/managesieve requests to backend Dovecot servers. > > I setup load-balance cluster for clients with HAProxy + KeepAlived + Dovecot > Director running in frontend servers, so sad we have to find an alternative > to replace Director in such case. > > It's not about "small/medium" servers, but the demand of imap/pop3/lmtp proxy > service, especially in load-balance cluster. > > > Zhang Huangbin, founder of: > - iRedMail: Open source email server solution: https://www.iredmail.org/ > - Spider: Lightweight, on-premises Email Archiving Software: > https://spiderd.io > >
Re: The end of Dovecot Director?
> On Oct 21, 2022, at 4:19 AM, Antonio Leding wrote: > > My understanding is that Director is targeted toward large enterprise mail > installations that will incorporate several servers for a given function. In > such an environment, Director would be the fore-person\traffic-cop keeping > things organized & squared-away. Director is used when you setup frontend servers in a load-balance cluster, proxy imap/pop3/lmtp/managesieve requests to backend Dovecot servers. I setup load-balance cluster for clients with HAProxy + KeepAlived + Dovecot Director running in frontend servers, so sad we have to find an alternative to replace Director in such case. It's not about "small/medium" servers, but the demand of imap/pop3/lmtp proxy service, especially in load-balance cluster. Zhang Huangbin, founder of: - iRedMail: Open source email server solution: https://www.iredmail.org/ - Spider: Lightweight, on-premises Email Archiving Software: https://spiderd.io
Re: The end of Dovecot Director?
My understanding is that Director is targeted toward large enterprise mail installations that will incorporate several servers for a given function. In such an environment, Director would be the fore-person\traffic-cop keeping things organized & squared-away. In other scenarios, the “pri\bu” means primary and backup DC instances which should be fine for many folks who just have a single server. Again this is my understanding so please feel free to correct me where I’m off-base… - - - On 20 Oct 2022, at 12:00, Steve Litt wrote: Aki Tuomi said on Thu, 20 Oct 2022 21:41:53 +0300 (EEST) Most small/medium servers do not need director. You can use replicator get a pri/bu pair. I've never needed to use replicator. I don't even know what a pri/bu pair is. I just have fetchmail feed to procmail which delivers messages into my Dovecot maildir, and then access the Dovecot IMAP server with an email client. Hopefully I'll be able to continue doing it this way. Only the director part is being removed, rest of Dovecot remains. For the next major release we are also removing certain deprecated parts that have a replacement in elsewhere of the code. Is there a document on the deprecations and their replacements? I'd like to read it. The mail server functionality is going to remain 100% open source and free. The preceding sentence is a huge relief for me. Thanks! SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm
Re: The end of Dovecot Director?
Aki Tuomi said on Thu, 20 Oct 2022 22:04:42 +0300 (EEST) >https://doc.dovecot.org/3.0/installation_guide/upgrading/from-2.3-to-3.0/ > >This is subject to change, as we have not actually released this >version yet. > >Aki Thanks Aki, I skimmed this document and it looks to me like nothing there applies to my Dovecot setup. I'll be checking it from time to time. Thanks, SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm
Re: The end of Dovecot Director?
> On 20/10/2022 22:00 EEST Steve Litt wrote: > > > Aki Tuomi said on Thu, 20 Oct 2022 21:41:53 +0300 (EEST) > > >Most small/medium servers do not need director. You can use replicator > >get a pri/bu pair. > > I've never needed to use replicator. I don't even know what a pri/bu > pair is. I just have fetchmail feed to procmail which delivers messages > into my Dovecot maildir, and then access the Dovecot IMAP server with > an email client. Hopefully I'll be able to continue doing it this way. > > > > >Only the director part is being removed, rest of Dovecot remains. For > >the next major release we are also removing certain deprecated parts > >that have a replacement in elsewhere of the code. > > Is there a document on the deprecations and their replacements? I'd > like to read it. > > > > >The mail server functionality is going to remain 100% open source and > >free. > > The preceding sentence is a huge relief for me. Thanks! > > SteveT > https://doc.dovecot.org/3.0/installation_guide/upgrading/from-2.3-to-3.0/ This is subject to change, as we have not actually released this version yet. Aki
Re: The end of Dovecot Director?
Aki Tuomi said on Thu, 20 Oct 2022 21:41:53 +0300 (EEST) >Most small/medium servers do not need director. You can use replicator >get a pri/bu pair. I've never needed to use replicator. I don't even know what a pri/bu pair is. I just have fetchmail feed to procmail which delivers messages into my Dovecot maildir, and then access the Dovecot IMAP server with an email client. Hopefully I'll be able to continue doing it this way. > >Only the director part is being removed, rest of Dovecot remains. For >the next major release we are also removing certain deprecated parts >that have a replacement in elsewhere of the code. Is there a document on the deprecations and their replacements? I'd like to read it. > >The mail server functionality is going to remain 100% open source and >free. The preceding sentence is a huge relief for me. Thanks! SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm
RE: The end of Dovecot Director?
> Most small/medium servers do not need director. You can use replicator > get a pri/bu pair. > What is small?
Re: The end of Dovecot Director?
Most small/medium servers do not need director. You can use replicator get a pri/bu pair. Only the director part is being removed, rest of Dovecot remains. For the next major release we are also removing certain deprecated parts that have a replacement in elsewhere of the code. The mail server functionality is going to remain 100% open source and free. Aki > On 20/10/2022 21:37 EEST Steve Litt wrote: > > > I'm top posting because I can't make heads or tails of this thread. > Does this thread mean that Dovecot will no longer be Free Software? > > It appears that only Dovecot Director will be taken proprietary, but if > all of Dovecot is in jeopardy, I need to switch to another local IMAP > server program. Any suggestions will be welcome. > > Thanks, > > SteveT > > > Aki Tuomi said on Thu, 20 Oct 2022 13:02:38 +0300 (EEST) > > >> On 20/10/2022 12:24 EEST Steff Majeur > >> wrote: > >> > >> > >> I recently stumbled upon the following commit on the Dovecot core > >> Github repository: > >> https://github.com/dovecot/core/commit/4a187116dc2311804be22724007d357323005358 > >> > >> Apparently, Dovecot Director is going to be removed in the next > >> major version of Dovecot and the commercial Dovecot cluster > >> architecture will be its successor: > >> https://github.com/dovecot/documentation/blob/a85b742ec4fc2744db30a6943b3c25f004e46720/source/admin_manual/cluster/index.rst > >> > > > >Yes, this is going to happen. > > > >> This would be a huge blow for many organizations around the world > >> that are currently using Dovecot with Director in a shared storage > >> environment. > >> > >> Can anyone of the Dovecot developers maybe enlighten us about the > >> future of Dovecot? > >> - Will there still be the Director feature in the next community > >> release of Dovecot? > > > >Next 2.3 CE release will have a director. > > > >> - If not, will there be a community feature that is on par with the > >> current Director feature? > > > >There will be more information about this closer to new major release, > >that we are working on. Director is still present in > >https://github.com/dovecot/core/tree/release-2.3 > > > >> - For how long will Dovecot version 2.3 still be supported (security > >> fixes, bug fixes)? Is there any EOL plan? > > > >This will be informed later, but as general rule, once we make a new > >major release, 2.3 will go into maintenance mode, and will receive > >only select bug fixes and CVE fixes. > > > >> Thanks for any clarification! > >> Steff > > > >Aki > > > SteveT > > Steve Litt > Summer 2022 featured book: Thriving in Tough Times > http://www.troubleshooters.com/bookstore/thrive.htm
Re: The end of Dovecot Director?
I'm top posting because I can't make heads or tails of this thread. Does this thread mean that Dovecot will no longer be Free Software? It appears that only Dovecot Director will be taken proprietary, but if all of Dovecot is in jeopardy, I need to switch to another local IMAP server program. Any suggestions will be welcome. Thanks, SteveT Aki Tuomi said on Thu, 20 Oct 2022 13:02:38 +0300 (EEST) >> On 20/10/2022 12:24 EEST Steff Majeur >> wrote: >> >> >> I recently stumbled upon the following commit on the Dovecot core >> Github repository: >> https://github.com/dovecot/core/commit/4a187116dc2311804be22724007d357323005358 >> >> Apparently, Dovecot Director is going to be removed in the next >> major version of Dovecot and the commercial Dovecot cluster >> architecture will be its successor: >> https://github.com/dovecot/documentation/blob/a85b742ec4fc2744db30a6943b3c25f004e46720/source/admin_manual/cluster/index.rst >> > >Yes, this is going to happen. > >> This would be a huge blow for many organizations around the world >> that are currently using Dovecot with Director in a shared storage >> environment. >> >> Can anyone of the Dovecot developers maybe enlighten us about the >> future of Dovecot? >> - Will there still be the Director feature in the next community >> release of Dovecot? > >Next 2.3 CE release will have a director. > >> - If not, will there be a community feature that is on par with the >> current Director feature? > >There will be more information about this closer to new major release, >that we are working on. Director is still present in >https://github.com/dovecot/core/tree/release-2.3 > >> - For how long will Dovecot version 2.3 still be supported (security >> fixes, bug fixes)? Is there any EOL plan? > >This will be informed later, but as general rule, once we make a new >major release, 2.3 will go into maintenance mode, and will receive >only select bug fixes and CVE fixes. > >> Thanks for any clarification! >> Steff > >Aki SteveT Steve Litt Summer 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm
Re: The end of Dovecot Director?
> On 20/10/2022 12:24 EEST Steff Majeur wrote: > > > I recently stumbled upon the following commit on the Dovecot core Github > repository: > https://github.com/dovecot/core/commit/4a187116dc2311804be22724007d357323005358 > > Apparently, Dovecot Director is going to be removed in the next major version > of Dovecot and the commercial Dovecot cluster architecture will be its > successor: > https://github.com/dovecot/documentation/blob/a85b742ec4fc2744db30a6943b3c25f004e46720/source/admin_manual/cluster/index.rst > Yes, this is going to happen. > This would be a huge blow for many organizations around the world that are > currently using Dovecot with Director in a shared storage environment. > > Can anyone of the Dovecot developers maybe enlighten us about the future of > Dovecot? > - Will there still be the Director feature in the next community release of > Dovecot? Next 2.3 CE release will have a director. > - If not, will there be a community feature that is on par with the current > Director feature? There will be more information about this closer to new major release, that we are working on. Director is still present in https://github.com/dovecot/core/tree/release-2.3 > - For how long will Dovecot version 2.3 still be supported (security fixes, > bug fixes)? Is there any EOL plan? > This will be informed later, but as general rule, once we make a new major release, 2.3 will go into maintenance mode, and will receive only select bug fixes and CVE fixes. > Thanks for any clarification! > Steff Aki
The end of Dovecot Director?
I recently stumbled upon the following commit on the Dovecot core Github repository: https://github.com/dovecot/core/commit/4a187116dc2311804be22724007d357323005358 Apparently, Dovecot Director is going to be removed in the next major version of Dovecot and the commercial Dovecot cluster architecture will be its successor: https://github.com/dovecot/documentation/blob/a85b742ec4fc2744db30a6943b3c25f004e46720/source/admin_manual/cluster/index.rst This would be a huge blow for many organizations around the world that are currently using Dovecot with Director in a shared storage environment. Can anyone of the Dovecot developers maybe enlighten us about the future of Dovecot? - Will there still be the Director feature in the next community release of Dovecot? - If not, will there be a community feature that is on par with the current Director feature? - For how long will Dovecot version 2.3 still be supported (security fixes, bug fixes)? Is there any EOL plan? Thanks for any clarification! Steff