This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 5 and 6
Revision 5 as of 2016-02-10 04:55:08
Size: 940
Editor: c-73-34-144-29
Comment: Add note on precedence
Revision 6 as of 2016-02-10 09:12:42
Size: 941
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Note: if you want to entirely block the user from logging in (i.e. account is suspended), with no IMAP referral information provided, you must ensure that neither {{{proxy}}} or {{{host}}} are defined as one of the passdb extra fields. The order of preference is: {{{proxy}}}, {{{host}}}, then {{{nologin}}}. Note: if you want to entirely block the user from logging in (i.e. account is suspended), with no IMAP referral information provided, you must ensure that neither {{{proxy}}} nor {{{host}}} are defined as one of the passdb extra fields. The order of preference is: {{{proxy}}}, {{{host}}}, then {{{nologin}}}.

Nologin extra field

User isn't allowed to log in even if the password matches. Commonly used with proxying and login referrals, but may also be used standalone. One way to use this would be perhaps:

  • nologin=y

  • reason=System is being upgraded, please try again later.

Unfortunately many clients don't show the reason to the user at all and just assume that the password was given wrong, so it might not be a good idea to use this unless the system will be down for days and you don't have a better way to notify the users.

Note: if you want to entirely block the user from logging in (i.e. account is suspended), with no IMAP referral information provided, you must ensure that neither proxy nor host are defined as one of the passdb extra fields. The order of preference is: proxy, host, then nologin.

None: PasswordDatabase/ExtraFields/NoLogin (last edited 2022-02-04 22:52:54 by TimoSirainen)