converted to 1.6 markup
use a cleaner ldap proxy example
|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
|Line 20:||Line 19:|
|=== SQL ===
|Line 21:||Line 22:|
|=== SQL ===
|Line 29:||Line 27:|
|=== LDAP ===
|Line 30:||Line 30:|
|=== LDAP ===||format is <ldap attribute 1>=<dovecot field 1>,<ldap attribute 2>=<dovecot field 2>,...|
|Line 32:||Line 32:|
|Line 34:||Line 33:|
|Line 36:||Line 35:|
|Note about the "proxy" or "proxy_maybe" fields: these represent an existence test.|
|Line 37:||Line 37:|
|In LDAP, this translates to "will proxy (or proxy_maybe) if this attribute exists". This allows the proxy behaviour to be selectable per user. To have it "always" on, use a template, e.g.:
|Line 38:||Line 43:|
Password database extra fields
The primary purpose of a password database lookup is to return the password for a given user. It may however also return other fields which are treated specially:
user: Change the username (eg. lowercase it).
allow_nets: Allow user to log in from only specified IPs.
proxy and proxy_maybe: Proxy the connection to another IMAP/POP3 server.
host: Send login referral to client.
nologin: User isn't actually allowed to log in even if the password matches, with optionally a different reason given as the authentication failure message.
nodelay: Don't delay reply to client in case of an authentication failure.
- nopassword: v1.1+: If you want to allow all passwords, use an empty password and this field.
The password database may also return fields prefixed with userdb_. These fields are only saved and used later as if they came from the user database's extra fields. Typically this is done only when using prefetch userdb.
Note that boolean fields are true always if the field exists. So nodelay, nodelay=yes, nodelay=no and nodelay=0 all mean that the nodelay field is true. With SQL the field is considered to be non-existent if its value is NULL.
password_query = SELECT userid as user, password, 'Y' as proxy, host \ FROM users WHERE userid = '%u' # NOTE: Dovecot doesn't really support line splitting with '\' currently
format is <ldap attribute 1>=<dovecot field 1>,<ldap attribute 2>=<dovecot field 2>,...
Note about the "proxy" or "proxy_maybe" fields: these represent an existence test.
In LDAP, this translates to "will proxy (or proxy_maybe) if this attribute exists". This allows the proxy behaviour to be selectable per user. To have it "always" on, use a template, e.g.: