Contents
How to use dovecot in a SQL Server?
SQL ¶ 1 Dovecot configuration ¶ 2 Password database lookups ¶. It must return a field named password. 3 Password verification by SQL server ¶. 4 User database lookups ¶. 5 User iteration ¶. 6 Prefetching ¶. 7 High availability ¶. 8 Examples ¶ 9 MySQL ¶. 10 PostgreSQL ¶
What is the default file name for Dovecot sieve?
If the main user’s personal Sieve (as configured with sieve) is a file, the logfile is set to .log by default. If it is not a file, the default user log file is ~/.dovecot.sieve.log. The separator that is expected between the :user and :detail address parts introduced by the subaddress extension.
Is there way to return user field in Dovecot?
To fix this, you can make the SQL database return a User extra field, which makes Dovecot modify the username to the returned value. If you’re using separate user and domain fields, a common problem is that you’re returning only the user field from the database.
Which is the default location for a sieve script?
The default file location type is a directory containing one or more Sieve script files with a symlink pointing to the active one. More complex setups can use other location types such as ldap or dict to fetch Sieve scripts from remote databases. All settings that specify the location of one or more Sieve scripts accept the following syntax:
Do you need to prefix a password with Dovecot?
The SQL and LDAP configuration files have the default_pass_scheme setting for this. If you have passwords in multiple formats, or the passdb doesn’t have such a setting, you’ll need to prefix each password with { }, Dovecot authenticates users against password databases.
How does Dovecot support caching passwords in Pam?
Dovecot supports caching password lookups by setting auth_cache_size to non-zero value. For this to work with PAM, you’ll also have to give cache_key parameter. Usually the user is authenticated only based on the username and password, but PAM plugins may do all kinds of other checks as well, so this can’t be relied on.
Can you read passwords from Shadow in Dovecot?
Shadow: Shadow passwords for system users (NSS, /etc/shadow or similiar). See Shadow. Dovecot supports reading all Password Schemes from passwd and shadow databases (if prefix is specified), but that is of course incompatible with all other tools using/modifying the passwords.
What to do if Dovecot doesn’t recognize a password?
If the passwords are in some special format in the SQL server that Dovecot doesn’t recognize, it’s still possible to use them. Change the SQL query to return NULL as the password and return the row only if the password matches. You’ll also need to return a non-NULL nopassword field.
What do you need to know about Dovecot directors?
Specifies the amount of memory used for authentication caching (passdb and userdb lookups). Space-separated list of IP/network ranges that contain the Dovecot Directors. This setting allows Directors to forward the client’s original IP address and session ID to the Backends.