> On 26/10/2022 11:41 EEST Narcis Garcia <debianlists at actiu.net> 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 can be used to proxy users to different backend server on which > > the users mailboxes are stored? > > > > Thanks Oliver > > > > Does this removal include or exclude IMAP backends? > > -- > > Narcis Garcia >No. The only thing removed is the director component. Proxying works, IMAP backends are not removed. Director is responsible for mapping users to particular hosts. This change will affect mostly people with more than 1-2 backends, with 2 backends you can still have primary/backup setup. Dovecot will still happily proxy connections to your backends. AKi
El 26/10/22 a les 10:51, Aki Tuomi ha escrit:> >> On 26/10/2022 11:41 EEST Narcis Garcia <debianlists at actiu.net> 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 can be used to proxy users to different backend server on which >>> the users mailboxes are stored? >>> >>> Thanks Oliver >>> >> >> Does this removal include or exclude IMAP backends? >> >> -- >> >> Narcis Garcia >> > > > No. The only thing removed is the director component. Proxying works, IMAP backends are not removed. Director is responsible for mapping users to particular hosts. > > This change will affect mostly people with more than 1-2 backends, with 2 backends you can still have primary/backup setup. Dovecot will still happily proxy connections to your backends. > > AKiMmhh what about this for same FQDN? one at example.net -> local Dovecot mailbox two at example.net -> local Dovecot mailbox three at example.net -> Specific IMAP backend four at example.net -> local Dovecot mailbox -- Narcis Garcia __________ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
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 the database if backend is down to move users elsewhere * When backend comes up, move users into it. Set delay_until extra field for user in passdb to 5 seconds into future and kick the user in its old backend (e.g. via doveadm HTTP API). All this can be done with existing Dovecot. Should be much easier to build a project doing this than forking director.