The dovecot_*_configuration variables define the contents of the :envvar:`dovecot_sql_password_query`, :envvar:`dovecot_sql_user_query`, and :envvar:`dovecot_sql_default_pass_scheme`, Other configuration parameters of interest are The database should have a structure like this: CREATE TABLE `users` ( # pgsql dovecot_sql_connect: 'host=192.168.1.1 dbname=users ' # mysql dovecot_sql_connect: 'host= dbname=virtual user=virtual password=blarg ' # sqlite dovecot_sql_connect: '/etc/dovecot/authdb.sqlite ' Is defined without the parameter=value format). sqlite Only one parameter is supported - the path to the database file (which You can connect to UNIX sockets by using host=/var/run/mysql.sock. option_group Read options from the given group (default: client). option_file Read options from the given file instead of the default :file:`my.cnf` ssl_verify_server_cert Verifies that the name in the server SSL certificate matches the host ssl_cipher Sets the minimum allowed cipher security (default: HIGH). ssl_cert, ssl_key For sending client-side certificates to the server. ssl_ca, ssl_ca_path Set either one or both to enable SSL. The basic options ( host, port, user, password, dbname)Īre the same as for pgsql, additional settings include: client_flags See the MySQL manual. maxconns The number of connections to create to the database (default 5). password The password to use when connecting to the database. user The username to use when connecting to the database. port The port on which the database server is listening. Pgsql host The host on which the database server is running. Possible to use spaces in parameters), with the possible parameters defined by Space-delimited string of parameter=value pairs (which means that it is not The parameters are generally provided as a Specific connection string needs to be defined in Users can be stored in an external SQL database (see checkpassword Users and passwords are stored in an external program. passwdfile Users and passwords are stored in a file. ldap Mail users are stored in the LDAP directory. sqlite Mail users are stored in a SQLite database (see pgsql Mail users are stored in a PostgreSQL database (see mysql Mail users are stored in a MySQL/MariaDB database (see system Mail users are Linux system users. dovecot_user_accountsĬurrently supported mechanisms for :envvar:`dovecot_user_accounts` are: deny Deny access for a statically defined list of users (see :envvar:`dovecot_dsync_password`, but these should all have sensible defaultsįor more information, see the Dovecot Replication wiki page. :envvar:`dovecot_dsync_replica`, :envvar:`dovecot_dsync_password_path` and Other variables are :envvar:`dovecot_dsync_port`, , setting something like this in your Ansible inventoryĭovecot_dsync_host: ' ' Assuming that you have two servers, named and Which needs to be set to point to the other server for each server in a sync The most important configuration variable is :envvar:`dovecot_dsync_host`, Together with a virtual email user since dsync would need root access Replication works only between server pairs. Replication is done by looking at Dovecot index files (not what exists in theįilesystem), so no mails get lost due to filesystem corruption or an accidentalĭeletion, they will simply be replicated back. The replication isĭone asynchronously, so high latency between the replicas isn't a problem. DSync Replicationĭovecot supports master/master replication using dsync. LMTP is recommended over LDA by the Dovecot project. Over imap and pop3 (explicit TLS) by RFC 8314. Note that imaps and pop3s (implicit TLS) are recommended Seeĭovecot's Replication Documentation for further details. :command:`dovecot` servers using :command:`dovecot`'s own dsync dsync Support for two-directional/pairwise dsync synchronization between two Seeĭovecot's Quota Plugin Documentation for further details. ManageSieve Documentation for further details. sieve Support for mail filtering/sorting using Sieve ( RFC 5228) scriptsĪnd the ManageSieve protocol ( RFC 5804, both with various extensionsįrom other RFCs), the latter typically using port 4190. pop3s POP3 with implicit TLS support, typically using port 995. pop3 POP3 ( RFC 1939, extensions from RFC 2449 and authenticationįrom RFC 1734) with explicit TLS support via STARTTLS, typically imaps IMAP4rev2 with implicit TLS support, typically using port 993. Than simple strings or lists, here you can find documentation and examples forĬurrently supported features for :envvar:`dovecot_features` are: imap IMAP4rev2 ( RFC 9051) with explicit TLS support via STARTTLS, Some of debops.dovecot default variables have more extensive configuration
0 Comments
Leave a Reply. |