Dovecot director and backend on same server

Hi, I'm attempting to run both the director and the backend under the same configuration on the same server. When I run doveadm director map I don't get any output. I have a shared file system between servers and clients can access any server. I was running without a director in front and see

dovecot director how to obtain hashed

Morning again! Working with my directors node. Does anybody now how to obtain a list of all users hashes? I know how to obtain for one user example: *doveadm director status user@domain* I am looking to a way or command to take a list of hashed epired (1)#: doveadm director status manolito@m

Re: The end of Dovecot Director?

If the community has enough resources to fork the whole project, it would probably be far more efficient and easier to just fork the Director component. I’m not familiar enough with dovecot sources to tell if this is possible, but if the community really wants to keep Director alive, maybe it s

Re: The end of Dovecot Director?

One of our developers wrote the whole LDAP integration in Dovecot, and I for one am not happy with this move. Jan Hugo On November 2, 2022 6:16:21 PM GMT+01:00, Dave McGuire wrote: > > It would certainly be a shame if that sort of thing started happening with > Dovecot. Since day one, the D

Re: The end of Dovecot Director?

It would certainly be a shame if that sort of thing started happening with Dovecot. Since day one, the Dovecot community has always been very pleasant, friendly, and drama-free. If forks start happening due to profiteering, that will irrevocably change the Dovecot community, with feeling

Re: The end of Dovecot Director?

I think the only thing they will gain is a community that is angry and will in the end leave the product / fork the complete product. Jan Hugo On November 2, 2022 5:39:53 PM GMT+01:00, Brad Schuetz wrote: >On 11/2/22 03:54, Aki Tuomi wrote: >>> On 02/11/2022 11:55 EET Frank Wall wrote: >>> >>

Re: The end of Dovecot Director?

On 11/2/22 03:54, Aki Tuomi wrote: On 02/11/2022 11:55 EET Frank Wall wrote: On 2022-11-02 09:11, Aki Tuomi wrote: You can also see the email sent by others which shows how you can do this without replication, using proxy and passdb to direct users to right backend. Which is basically what

Re: The end of Dovecot Director?

> On 02/11/2022 11:55 EET Frank Wall wrote: > > > On 2022-11-02 09:11, Aki Tuomi wrote: > > You can also see the email sent by others which shows how you can do > > this without replication, using proxy and passdb to direct users to > > right backend. Which is basically what director does. >

Re: The end of Dovecot Director?

On 2022-11-02 09:11, Aki Tuomi wrote: You can also see the email sent by others which shows how you can do this without replication, using proxy and passdb to direct users to right backend. Which is basically what director does. It's not the same thing. It is not critical functionality. You c

Re: The end of Dovecot Director?

> On 01/11/2022 17:58 EET Mark Moseley wrote: > > > TL;DR:  > > Sure, this affects medium/large/Enterprise folks (that's where I was using > Director -- though currently retired, so no existing self-interest in this > email). > > This will also affect *any* installation with a

Re: The end of Dovecot Director?

On 2022-11-01 16:58, Mark Moseley wrote: This *feels" to me like a parent company looking to remove features from the open source version in order to add feature differentiation to the paid version. I've loved the Dovecot project for over a decade and a half. And incidentally I have a very w

Re: The end of Dovecot Director?

Frank Wall skrev den 2022-11-01 23:44: On 2022-11-01 16:58, Mark Moseley wrote: TL;DR: I think the real issue here is that Dovecot is removing *existing, long-standing, critical functionality* from the open source version. That is a huge, huge red flag. It certainly looks like

Re: The end of Dovecot Director?

On 2022-11-01 16:58, Mark Moseley wrote: TL;DR: I think the real issue here is that Dovecot is removing *existing, long-standing, critical functionality* from the open source version. That is a huge, huge red flag. It certainly looks like a poor decision, driven by corporate int

Re: The end of Dovecot Director?

I think the real issue here is that Dovecot is removing _existing, long-standing, critical_ functionality from the open source version. That is a huge, huge red flag. Clear enough. It would be great if dovecot decides to keep it in one way or another in community release.

Re: The end of Dovecot Director?

TL;DR: Sure, this affects medium/large/Enterprise folks (that's where I was using Director -- though currently retired, so no existing self-interest in this email). This will also affect *any* installation with a whopping two dovecot servers with mdbox backends talking to a single li

Re: The end of Dovecot Director?

On 27.10.22 04:24, Timo Sirainen wrote: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) containing user -> backend table. * Configure Dovecot proxy to use this database a

Re: The end of Dovecot Director?

On 2022-10-27 08:31, William Edwards wrote:  Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende geschreven: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) cont

Re: The end of Dovecot Director?

On 2022-10-27 08:31, William Edwards wrote:  Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende geschreven: Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) cont

Re: The end of Dovecot Director?

 > Op 27 okt. 2022 om 04:25 heeft Timo Sirainen het volgende > geschreven: > > Director never worked especially well, and for most use cases it's just > unnecessarily complex. I think usually it could be replaced with: > > * Database (sql/ldap/whatever) containing user -> backend table. > *

Re: The end of Dovecot Director?

Director never worked especially well, and for most use cases it's just unnecessarily complex. I think usually it could be replaced with: * Database (sql/ldap/whatever) containing user -> backend table. * Configure Dovecot proxy to use this database as passdb. * For HA change dovemon to update

Re: The end of Dovecot Director?

Am 2022-10-26 11:52, schrieb Maciej Milaszewski: Will there be a fork dovecot ? Hm, maybe it would be possible to just fork the director component? But it would still require a passionate C developer. Whether LibreCot or FreeDirector will be born... I'd be happy to support both! And don't feel

Re: The end of Dovecot Director?

Maciej Milaszewski schreef op 2022-10-26 11:52: Hi What is the planned replacement like doveadm director status move / kick / flush add /up / del In 3.0 ? This question has been answered in the thread. Will there be a fork dovecot ? If we, the community, start one, yes. -- With kind reg

Re: The end of Dovecot Director?

Hi What is the planned replacement like doveadm director status move / kick / flush add /up / del In 3.0 ? Will there be a fork dovecot ? OpenPGP_signature Description: OpenPGP digital signature

Re: The end of Dovecot Director?

> On 26/10/2022 12:42 EEST Narcis Garcia wrote: > > > El 26/10/22 a les 10:51, Aki Tuomi ha escrit: > > > >> On 26/10/2022 11:41 EEST Narcis Garcia wrote: > >> > >> > >> El 26/10/22 a les 10:29, MK ha escrit: > To be clear, we are not removing proxying features from Dovecot either.

Re: The end of Dovecot Director?

El 26/10/22 a les 10:51, Aki Tuomi ha escrit: On 26/10/2022 11:41 EEST Narcis Garcia wrote: El 26/10/22 a les 10:29, MK ha escrit: To be clear, we are not removing proxying features from Dovecot either. Just the director ring feature. To be realy clear, you are not removing the proxy fe

Re: The end of Dovecot Director?

> On 26/10/2022 11:41 EEST Narcis Garcia wrote: > > > El 26/10/22 a les 10:29, MK ha escrit: > >> To be clear, we are not removing proxying features from Dovecot either. > >> Just the director ring feature. > > To be realy clear, you are not removing the proxy feature in dovecot that > > ca

Re: The end of Dovecot Director?

El 26/10/22 a les 10:29, MK ha escrit: To be clear, we are not removing proxying features from Dovecot either. Just the director ring feature. To be realy clear, you are not removing the proxy feature in dovecot that can be used to proxy users to different backend server on which the users mai

AW: The end of Dovecot Director?

Oct 21, 2022, at 5:23 PM, hi@zakaria.website wrote: > > >> > > >> I was wondering if one can achieve the same implementation with > > >> haproxy without dovecot director? > > > > > > The most important part of Director is it makes sure

Re: The end of Dovecot Director?

On 2022-10-21 13:25, dove...@ptld.com wrote: the problem that prevents most load balancers from handling the backend imap/pop traffic is that the load balancer needs to be aware of the context of each connection. which all boils down to the index files (only a single dovecot server can access a

Re: The end of Dovecot Director?

On 2022-10-24, Alessio Cecchi wrote: > > Director is not only used by large companies but also in small > installations consisting of 2 servers and cannot be immediately replaced > with Nginx as it has to manage the user/backend association for POP, > IMAP, LMTP, Managesieve. For the small mul

Re: The end of Dovecot Director?

On 2022-10-21 11:38, Heiko Schlittermann wrote: 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: We - the communitiy - are free to continue development of the director. So, who&#

Re: The end of Dovecot Director?

On 2022-10-21 10:54, Zhang Huangbin wrote: On Oct 21, 2022, at 5:51 PM, Zhang Huangbin wrote: If mailbox is in Maildir format (and stored on shared storage like NFS), accessing it from different server may corrupt Dovecot index files and mailbox becomes unaccessible. Director perfectly avoids

Re: The end of Dovecot Director?

the problem that prevents most load balancers from handling the backend imap/pop traffic is that the load balancer needs to be aware of the context of each connection. which all boils down to the index files (only a single dovecot server can access a set of index files concurrently, else the in

Re: The end of Dovecot Director?

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

Re: The end of Dovecot Director?

> Op 21 okt. 2022 om 19:42 heeft Brendan Braybrook het > volgende geschreven: > > On 2022-10-21 04:29, spi wrote: >>> Am 21.10.22 um 13:14 schrieb Amol Kulkarni: >>> Nginx has an mail proxy for pop, imap, smtp. >>> Can it be used instead of director ? >> Nginx can authenticate imap/smtp (and

Re: The end of Dovecot Director?

On 2022-10-21 04:29, spi wrote: Am 21.10.22 um 13:14 schrieb Amol Kulkarni: Nginx has an mail proxy for pop, imap, smtp. Can it be used instead of director ? Nginx can authenticate imap/smtp (and probably pop3) users. If you that, you can define a backend server the session is routed to. Curren

Re: The end of Dovecot Director?

Nginx is an excellent suggestion for the purpose. However I do not like German client certificates. That is far too much "proof" of identification 18/21++ on a public network with nowhere to hide and those of us who are not German citizens and do not have the advantage of a friendly local polic

Re: The end of Dovecot Director?

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

Re: The end of Dovecot Director?

, smtp. Can it be used instead of director ? On Fri, 21 Oct 2022 at 16:21, wrote: > On 2022-10-21 10:51, Zhang Huangbin wrote: > >> On Oct 21, 2022, at 5:23 PM, hi@zakaria.website wrote: > >> > >> I was wondering if one can achieve the same implementation with

Re: The end of Dovecot Director?

Am 21.10.22 um 13:14 schrieb Amol Kulkarni: Nginx has an mail proxy for pop, imap, smtp. Can it be used instead of director ? Nginx can authenticate imap/smtp (and probably pop3) users. If you that, you can define a backend server the session is routed to. Currently I use that approach to aut

Re: The end of Dovecot Director?

ct 2022 at 16:21, wrote: > > On 2022-10-21 10:51, Zhang Huangbin wrote: > > >> On Oct 21, 2022, at 5:23 PM, hi@zakaria.website wrote: > > >> > > >> I was wondering if one can achieve the same implementation with > > >> haproxy without do

Re: The end of Dovecot Director?

chieve the same implementation with > >> haproxy without dovecot director? > > > > The most important part of Director is it makes sure same mail user > > always proxied to same backend IMAP server. > > > > If mailbox is in Maildir format (and stored on shared

Re: The end of Dovecot Director?

On 2022-10-21 10:51, Zhang Huangbin wrote: On Oct 21, 2022, at 5:23 PM, hi@zakaria.website wrote: I was wondering if one can achieve the same implementation with haproxy without dovecot director? The most important part of Director is it makes sure same mail user always proxied to same

Re: The end of Dovecot Director?

> On Oct 21, 2022, at 5:51 PM, Zhang Huangbin wrote: > > If mailbox is in Maildir format (and stored on shared storage like NFS), > accessing it from different server may corrupt Dovecot index files and > mailbox becomes unaccessible. Director perfectly avoids this issue. To be clear: Acces

Re: The end of Dovecot Director?

> On Oct 21, 2022, at 5:23 PM, hi@zakaria.website wrote: > > I was wondering if one can achieve the same implementation with haproxy > without dovecot director? The most important part of Director is it makes sure same mail user always proxied to same backend IMAP server. If m

Re: The end of Dovecot Director?

Steff Majeur (Do 20 Okt 2022 11:24:49 CEST): > 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

Re: The end of Dovecot Director?

: Open source email server solution: https://www.iredmail.org/ - Spider: Lightweight, on-premises Email Archiving Software: https://spiderd.io Hi, I was wondering if one can achieve the same implementation with haproxy without dovecot director? Load balancing all requests to pop3, imap, managesiev

RE: The end of Dovecot Director?

> 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. The code is still available you just need to build it yoursel

Re: The end of Dovecot Director?

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

Re: The end of Dovecot Director?

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

Re: The end of Dovecot Director?

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

Re: The end of Dovecot Director?

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

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”

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

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

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

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?

+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/4a187116dc231

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 serv

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 t

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

Re: Dovecot Director: Preferred backend server

>From dovecot director point of view it does not make any difference if your >imap clusters have only one server each. mail_hosts takes IP addresses, DNS >names whatever, and you can assign tag per host if you want. And yes, if you have only one server for a tag, then your clients a

Re: Dovecot Director: Preferred backend server

with that tag? By the way, I did a quick live test and it does not even seem to work, when both hosts are up, failing with the log entry on the dovecot server: Aug 31 11:11:11 lb01 dovecot: director: Error: director: User t...@example.com host lookup failed: Timeout because no hosts - queue

Re: Dovecot Director: Preferred backend server

HAProxy is fundamentally different as it operates on connections only, which is not what you usually want on IMAP Servers. Instead you want to route all connections from the same USER to the same server and for this you must have a layer-7 proxy like dovecot director. The implication with

Re: Dovecot Director: Preferred backend server

o the same > backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server1? > > thanks in advance, > St

Re: Dovecot Director: Preferred backend server

tor usually routes a client/user to the same > backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server

Re: Dovecot Director: Preferred backend server

> backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server1? > > thanks in advance, > Steven > > -- > https://steven.varco.ch/ > https://www.tech-island.com/ > >

Re: Dovecot Director: Preferred backend server

not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user goes to server1 or se

Dovecot Director: Preferred backend server

so far. If not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user go

Re: dovecot director and keepalived

t to 2.3 (which I believe should habe the smtp sumbmission service included). And it is also used for proxing to other services, like http for webmail, etc. Regarding the dovecot setup, I just use keepalived -> dovecot director -> dovecot IMAP Sorry for the confusion, might should have men

Re: dovecot director and keepalived

Hi Steven, On 14/03/2021, 17:53, "dovecot on behalf of Steven Varco" wrote: > Now I’m hitting the issue with the way director determines his „Self IP“ by > trying to > bind to all configured director_servers IPs, taking the first one possible. > > However this approach only works, when the

Re: dovecot director and keepalived

Le 16/03/2021 à 12:47, Eirik Rye a écrit : > > > On 03/15/2021 8:43 PM, Paterakis E. Ioannis wrote: >> It's not keepalived's work to tell the directors which backend is >> up/down. You can use poolmon for that. keepalived will make sure the >> floating ip will always be assigned on an alive hapro

Re: dovecot director and keepalived

On 03/15/2021 8:43 PM, Paterakis E. Ioannis wrote: It's not keepalived's work to tell the directors which backend is up/down. You can use poolmon for that. keepalived will make sure the floating ip will always be assigned on an alive haproxy. Then it's haproxies' work to check the aliveness

Re: dovecot director and keepalived

tting your services to different VMs, and them to different hypervisors in order to be as Highly available as you can John The point of dovecot director is that it acts as a proxy that always routes users to same backend. You can use keepalived, if it supports external commands, to maybe tell dire

Re: dovecot director and keepalived

x27;s all. > > But, if you plan to make a Highly available environment, u have to > consider splitting your services to different VMs, and them to different > hypervisors in order to be as Highly available as you can > > John The point of dovecot director is that it acts as

Re: dovecot director and keepalived

On 15/3/2021 6:09 μ.μ., Steven Varco wrote: Hi John Thanks for you input. So you basically state that („physically“) separating the director servers from keepalive/haproxy servers is the only option? I would like to avoid setting up two additional machines for that whenever possible, as any

Re: dovecot director and keepalived

Am 14.03.21 um 17:52 schrieb Steven Varco: Hi All I’m trying to establish a dovecot HA setup with two loadbalancers, running keepalived for sharing a virtual public IP. On the same machines I’m running a dovecot director which proxies the requests to two underlying mail servers (on seperate

Re: dovecot director and keepalived

6:52 μ.μ., Steven Varco wrote: > >> Hi All >> >> I’m trying to establish a dovecot HA setup with two loadbalancers, running >> keepalived for sharing a virtual public IP. >> On the same machines I’m running a dovecot director which proxies the >> requ

Re: dovecot director and keepalived

On 14/3/2021 6:52 μ.μ., Steven Varco wrote: Hi All I’m trying to establish a dovecot HA setup with two loadbalancers, running keepalived for sharing a virtual public IP. On the same machines I’m running a dovecot director which proxies the requests to two underlying mail servers (on seperate

dovecot director and keepalived

Hi All I’m trying to establish a dovecot HA setup with two loadbalancers, running keepalived for sharing a virtual public IP. On the same machines I’m running a dovecot director which proxies the requests to two underlying mail servers (on seperate machines). Now I’m hitting the issue with the

Re: Infinity loop when run "doveadm quota get -A" from Dovecot Director with 500 users

is highly appreciated. I > modified source files which might be shared with other doveadm commands so > I'm not sure it's safe 100%. > > Thanks, > Anh Do > > > On Wed, 27 Jan 2021 at 16:20, Duc Anh Do wrote: > > Hi all, > > > > I have one

Re: Infinity loop when run "doveadm quota get -A" from Dovecot Director with 500 users

27 Jan 2021 at 16:20, Duc Anh Do wrote: > Hi all, > > I have one Dovecot Director, two Dovecot Backends and one LDAP server with > about 500 users. I would like to run *doveadm quota get -A* from the > Director. > In each Backend, there is no problem when run the command: >

Infinity loop when run "doveadm quota get -A" from Dovecot Director with 500 users

Hi all, I have one Dovecot Director, two Dovecot Backends and one LDAP server with about 500 users. I would like to run *doveadm quota get -A* from the Director. In each Backend, there is no problem when run the command: # doveadm quota get -A user1 User quota STORAGE 0 10485760

Re: Dovecot Director scaling / performance

us.de wrote: Hi, currently i'm going to evaluate the Dovecot Director. Are there someone with experience how the Dovecot Director does scale? The last current information i could find was a post on this mailing list from 2012: 4 Directors are well known, >75 are too much. Are there any mo

Dovecot Director scaling / performance

Hi, currently i'm going to evaluate the Dovecot Director. Are there someone with experience how the Dovecot Director does scale? The last current information i could find was a post on this mailing list from 2012: 4 Directors are well known, >75 are too much. Are there any more up

Re: How to setup Dovecot director in a NAT-like environment?

> On 05/12/2020 14:41 Richard Mader wrote: > > > How can I setup Dovecot director in a NAT like environment? > > My mailservers are running within docker and one of them behind a > router, so the IP that dovecot binds to does not match the IP that other > ma

How to setup Dovecot director in a NAT-like environment?

How can I setup Dovecot director in a NAT like environment? My mailservers are running within docker and one of them behind a router, so the IP that dovecot binds to does not match the IP that other mailservers have to use to connect to them. Since when running director the servers connect

Re: Dovecot Director upgrade from 2.2 to 2.3

Il 22/07/19 18:49, Timo Sirainen ha scritto: On 22 Jul 2019, at 17.45, Alessio Cecchi > wrote: one server of the ring is now running Dovecot 2.3.7 and works fine with the others Dovecot 2.2 since 3 days. I notice only that the load avarage of this CentOS 7 server is h

Re: Dovecot Director upgrade from 2.2 to 2.3

On 31 Jul 2019, at 15.41, Alessio Cecchi via dovecot wrote: > > Hi Timo, > > here you can see two images with the load average and CPU usage with Dovecot > 2.2 (Centos 6) and 2.3 (Centos 7) on the same hardware and same configuration: > > https://imgur.com/a/1hsItlc

Re: Dovecot Director upgrade from 2.2 to 2.3

Hi Timo, here you can see two images with the load average and CPU usage with Dovecot 2.2 (Centos 6) and 2.3 (Centos 7) on the same hardware and same configuration: https://imgur.com/a/1hsItlc Load average increment is relevant but CPU usage is similar. Il 22/07/19 18:49, Timo Sirainen ha s

Re: Dovecot Director upgrade from 2.2 to 2.3

On 22 Jul 2019, at 17.45, Alessio Cecchi wrote: > > one server of the ring is now running Dovecot 2.3.7 and works fine with the > others Dovecot 2.2 since 3 days. > I notice only that the load avarage of this CentOS 7 server is higher > compared with CentOS 6 and Dovecot 2.2, but I don't know i

Re: Dovecot Director upgrade from 2.2 to 2.3

Il 18/07/19 21:42, Timo Sirainen ha scritto: On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot mailto:dovecot@dovecot.org>> wrote: Hi, I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) Now I would like to upgrade to 2.3.7, first only Direct

Re: Dovecot Director upgrade from 2.2 to 2.3

On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot wrote: > > Hi, > > I have a setup with 3 Dovecot Director v2.2.36 and > director_consistent_hashing = yes ;-) > > Now I would like to upgrade to 2.3.7, first only Director and after also > Backend. > > Can

Dovecot Director upgrade from 2.2 to 2.3

Hi, I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) Now I would like to upgrade to 2.3.7, first only Director and after also Backend. Can works fine a ring of director with mixed 2.2 and 2.3 version? Mi idea is to setup a new Director server with

Re: Dovecot director: show user breakdown by director?

This is only available if you use "verbose_proctitle = yes". However, I found the command "doveadm proxy list" which does what I want: ~# doveadm proxy list | wc -l 16993 - Eirik On 14/06/2019 08:39, Sami Ketola wrote: On 13 Jun 2019, at 20.15, Eirik Rye via dovecot

Re: Dovecot director: show user breakdown by director?

> On 13 Jun 2019, at 20.15, Eirik Rye via dovecot wrote: > Is there a way in Dovecot to see which (or even how many) users are connected > to a specific director without having to count TCP connections? # ps aux | grep imap-login dovenull 3200 0.0 0.0 44676 3376 ?SApr16 1:15

Dovecot director: show user breakdown by director?

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but ther

Re: Issue with dovecot/director

> > >   > > > > Hi, > > > > > > are there any known issues with dovecot/director (2.2.13) when > > > receiving e-an mail with multiple receivers? In the given scenario > > > the > > > e-mail contains 3 recipients and is redirected by t

Re: Issue with dovecot/director

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Montag, den 01.04.2019, 19:36 +0300 schrieb Aki Tuomi: > > On 1 April 2019 19:29 Nico Stöckigt via dovecot > g> wrote: > > > >   > > Hi, > > > > are there any known issues with dovecot/director

Re: Issue with dovecot/director

> On 1 April 2019 19:29 Nico Stöckigt via dovecot wrote: > > Hi, > > are there any known issues with dovecot/director (2.2.13) when > receiving e-an mail with multiple receivers? In the given scenario the > e-mail contains 3 recipients and is redirected by the director

  1   2   3   4   >