Hello,
I am using Dovecot 2.3.7.2, configure with Director and Dovecot backend.
Everything is running fine through director. However, I found the auth
cache flush command can only work on dovecot backend server but not in
Director. Any idea?
- Joe
Plutocrat skrev den 2020-01-07 03:33:
https://doc.dovecot.org/configuration_manual/authentication/pam/
https://github.com/google/google-authenticator-libpam
it scales not very well to limit 2fa to only pam users, dovecot support
many other auth backends and imho dovecot should never use 2fa,
You don't say what sort of 2FA you're considering, but wouldn't you just tell
Dovecot to use PAM, and then extend PAM to use a 2FA module. For example
there's a Google Auth one available in the second link below.
https://doc.dovecot.org/configuration_manual/authentication/pam/
https://github.com
Hi,
My goal is to protect my mail account with 2FA, which isn't a crazy
idea in 2020. Therefore, I would like to know the possibilities of
configuring 2FA for Dovecot. In the documentation there are some hints
of e.g. OTP in Dovecot [1] and using FreeIPA with Dovecot [2], where
FreeIPA has the a
Hi,
After upgrading Dovecot from version 2.2.27 to 2.3.9.2, we are
sporadically seeing lots of these errors in the error log on many of our
servers:
imap-login: Error: master(imap): net_connect_unix(imap) failed:
Resource temporarily unavailable -
http://wiki2.dovecot.org/SocketUnavailabl
