[GH-ISSUE #1726] use of doveadm blocks using modoboa on his own server #1362

New issue

Closed

opened 2026-02-27 11:16:43 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 11:16:43 +03:00

Owner

Originally created by @cl-parsons on GitHub (Apr 26, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1726

I just discovered today, by trying to change the password scheme in modoboa, that it would check the available dovecot password schemes by launching the doveadm command.

I run modoboa on his own server, to avoid interfering with my postfix/dovecot setup. Since doveadm is a local tool on the dovecot server, it is not possible for modoboa to check the available schemes, and therefore, to change de password scheme.

I think that keeping the ability to run on a remote dovecot server is a good thing, now I am somehow forced to fork modoba and remove this check. Maybe there could be a better option to keep everything together, but for now it seems better for me just to remove it.

Thanks for the work!

Originally created by @cl-parsons on GitHub (Apr 26, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1726 I just discovered today, by trying to change the password scheme in modoboa, that it would check the available dovecot password schemes by launching the doveadm command. I run modoboa on his own server, to avoid interfering with my postfix/dovecot setup. Since doveadm is a local tool on the dovecot server, it is not possible for modoboa to check the available schemes, and therefore, to change de password scheme. I think that keeping the ability to run on a remote dovecot server is a good thing, now I am somehow forced to fork modoba and remove this check. Maybe there could be a better option to keep everything together, but for now it seems better for me just to remove it. Thanks for the work!