This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 13 and 15 (spanning 2 versions)
Revision 13 as of 2010-06-14 20:33:18
Size: 1136
Editor: TimoSirainen
Comment:
Revision 15 as of 2017-02-05 16:57:13
Size: 1535
Editor: adsl-75-24-144-2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Most commonly used as a user database. Many systems use shadow passwords nowadays so it doesn't usually work as a password database. BSDs are an exception to this, they still set the password field even with shadow passwords. Most commonly used as a user database.
Line 15: Line 15:
== Field overriding and extra fields ==
It's possible to override fields from passwd and add [[UserDatabase/ExtraFields|extra fields]] with templates. For example:
== Field overriding and extra fields (obsolete in v2.1+) ==
It's possible to override fields from passwd and add [[UserDatabase/ExtraFields|extra fields]] with templates, but in v2.1+ it's done in a better way by using override_fields. For example:
Line 21: Line 21:
  args = home=/var/mail/%u mail=maildir:/var/mail/%u/Maildir   # Pre-v2.1:
  #
args = home=/var/mail/%u mail=maildir:/var/mail/%u/Maildir
  # v2.1+:
  override_fields = home=/var/mail/%u mail=maildir:/var/mail/%u/Maildir
Line 25: Line 28:

== Passwd as a password database ==
Many systems use shadow passwords nowadays so passwd doesn't usually work as a password database. BSDs are an exception to this, they still set the password field even with shadow passwords.

With FreeBSD, passwd doesn't work as a password database because the password field is replaced by a *. Instead, you can use [[AuthDatabase/PasswdFile|Passwd-file]].

Passwd

User is looked up using getpwnam() call, which usually looks into /etc/passwd file, but depending on NSS configuration it may also look up the user from eg. LDAP database.

Most commonly used as a user database.

The lookup is by default done in the auth worker processes. If you have only a small local passwd file, you can avoid having extra auth worker processes by disabling it:

userdb {
  driver = passwd
  args = blocking=no
}

Field overriding and extra fields (obsolete in v2.1+)

It's possible to override fields from passwd and add extra fields with templates, but in v2.1+ it's done in a better way by using override_fields. For example:

userdb {
  driver = passwd
  # Pre-v2.1:
  #args = home=/var/mail/%u mail=maildir:/var/mail/%u/Maildir
  # v2.1+:
  override_fields = home=/var/mail/%u mail=maildir:/var/mail/%u/Maildir
}

This uses the UID and GID fields from passwd, but home directory is overridden. Also the default mail_location setting is overridden.

Passwd as a password database

Many systems use shadow passwords nowadays so passwd doesn't usually work as a password database. BSDs are an exception to this, they still set the password field even with shadow passwords.

With FreeBSD, passwd doesn't work as a password database because the password field is replaced by a *. Instead, you can use Passwd-file.

None: AuthDatabase/Passwd (last edited 2019-09-11 14:08:34 by MichaelSlusarz)