dovecot-example.conf revision 861d373feea39d3fe8c3cda75ea25cf418a2e26c
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo## Dovecot 1.0 configuration file
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Default values are shown after each value, it's not required to uncomment
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# any of the lines. Exception to this are paths, they're just examples
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# with real defaults being based on configure options. The paths listed here
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# --with-ssldir=/etc/ssl
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Base directory where to store runtime data.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#base_dir = /var/run/dovecot/
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Protocols we want to be serving:
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# imap imaps pop3 pop3s
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#protocols = imap imaps
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# IP or host address where to listen in for connections. It's not currently
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# possible to specify multiple addresses. "*" listens in all IPv4 interfaces.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# interfaces depending on the operating system. You can specify ports with
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# "host:port".
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#listen = *
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# IP or host address where to listen in for SSL connections. Defaults
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# to above if not specified.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_listen =
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Disable SSL/TLS support.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_disable = no
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# dropping root privileges, so keep the key file unreadable by anyone but
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# root. Included doc/mkcert.sh can be used to easily generate self-signed
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# certificate, just make sure to update the domains in dovecot-openssl.cnf
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_cert_file = /etc/ssl/certs/dovecot.pem
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_key_file = /etc/ssl/private/dovecot.pem
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# SSL parameter file. Master process generates this file for login processes.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# It contains Diffie Hellman and RSA parameters.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# How often to regenerate the SSL parameters file. Generation is quite CPU
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# intensive operation. The value is in hours, 0 disables regeneration
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# entirely.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_parameters_regenerate = 24
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# SSL ciphers to use
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#ssl_cipher_list = all:!low
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Disable LOGIN command and all other plaintext authentications unless
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# IPv6 ::1 addresses are considered secure, this setting has no effect if
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# you connect from those addresses.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#disable_plaintext_auth = yes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Use this logfile instead of syslog(). /dev/stderr can be used if you want to
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# use stderr for logging (ONLY /dev/stderr - otherwise it is closed).
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#log_path =
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# For informational messages, use this logfile instead of the default
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#info_log_path =
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Prefix for each line written to log file. % codes are in strftime(3)
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# format.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#log_timestamp = "%b %d %H:%M:%S "
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo##
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo## Login processes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo##
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Directory where authentication process places authentication UNIX sockets
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# which login needs to be able to connect to. The sockets are created when
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# running as root, so you don't have to worry about permissions.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_dir = /var/run/dovecot/login
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# chroot login process to the login_dir. Only reason not to do this is if you
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# wish to run the whole Dovecot without roots.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_chroot = yes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# User to use for the login process. Create a completely new user for this,
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# and don't use it anywhere else. The user must also belong to a group where
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# only it has access, it's used to control access for authentication process.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_user = dovecot
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Set max. process size in megabytes. If you don't use
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# login_process_per_connection you might need to grow this.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_process_size = 16
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Should each login be processed in it's own process (yes), or should one
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# login process be allowed to process multiple connections (no)? Yes is more
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# secure, espcially with SSL/TLS enabled. No is faster since there's no need
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# to create processes all the time.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_process_per_connection = yes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Number of login processes to create. If login_process_per_user is
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# yes, this is the number of extra processes waiting for users to log in.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_processes_count = 3
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Maximum number of extra login processes to create. The extra process count
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# usually stays at login_processes_count, but when multiple users start logging
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# in at the same time more extra processes are created. To prevent fork-bombing
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# we check only once in a second if new processes should be created - if all
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# of them are used at the time, we double their amount until limit set by this
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# setting is reached. This setting is used only if login_process_per_use is yes.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_max_processes_count = 128
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Maximum number of connections allowed in login state. When this limit is
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# reached, the oldest connections are dropped. If login_process_per_user
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# is no, this is a per-process value, so the absolute maximum number of users
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# logging in actually login_processes_count * max_logging_users.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#login_max_logging_users = 256
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo##
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo## Mail processes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo##
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Maximum number of running mail processes. When this limit is reached,
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# new users aren't allowed to log in.
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#max_mail_processes = 1024
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# Show more verbose process titles (in ps). Currently shows user name and
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# IP address. Useful for seeing who are actually using the IMAP processes
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo# (eg. shared mailboxes or if same uid is used for multiple accounts).
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo#verbose_proctitle = no
2b371b262f7272266ff18cc2aff65176a2c16383Sungbae Yoo
# Show protocol level SSL errors.
#verbose_ssl = no
# Valid UID range for users, defaults to 500 and above. This is mostly
# to make sure that users can't log in as daemons or other system users.
# Note that denying root logins is hardcoded to dovecot binary and can't
# be done even if first_valid_uid is set to 0.
#first_valid_uid = 500
#last_valid_uid = 0
# Valid GID range for users, defaults to non-root/wheel. Users having
# non-valid GID as primary group ID aren't allowed to log in. If user
# belongs to supplementary groups with non-valid GIDs, those groups are
# not set.
#first_valid_gid = 1
#last_valid_gid = 0
# ':' separated list of directories under which chrooting is allowed for mail
# processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too).
# This setting doesn't affect login_chroot or auth_chroot variables.
# WARNING: Never add directories here which local users can modify, that
# may lead to root exploit. Usually this should be done only if you don't
# allow shell access for users. See doc/configuration.txt for more information.
#valid_chroot_dirs =
# Default chroot directory for mail processes. This can be overridden by
# giving /./ in user's home directory (eg. /home/./user chroots into /home).
#mail_chroot =
# Default MAIL environment to use when it's not set. By leaving this empty
# dovecot tries to do some automatic detection as described in
# doc/mail-storages.txt. There's a few special variables you can use:
#
# %u - username
# %n - user part in user@domain, same as %u if there's no domain
# %d - domain part in user@domain, empty if user there's no domain
# %h - home directory
#
# You can also limit a width of string by giving the number of max. characters
# after the '%' character. For example %1u gives the first character of
# username. Some examples:
#
# default_mail_env = maildir:/var/mail/%1u/%u/Maildir
# default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u
# default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n
#
#default_mail_env =
# Space-separated list of fields to cache for all mails. Currently these
# fields are allowed followed by a list of commands they speed up:
#
# Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT,
# SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID,
# HEADER IN-REPLY-TO
# Body - FETCH BODY
# Bodystructure - FETCH BODY, BODYSTRUCTURE
# MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE,
# SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE
# generation. This is always set with mbox mailboxes, and
# also default with Maildir.
#
# Different IMAP clients work in different ways, that's why Dovecot by default
# only caches MessagePart which speeds up most operations. Whenever client
# does something where caching could be used, the field is automatically marked
# to be cached later. For example after FETCH BODY the BODY will be cached
# for all new messages. Normally you should leave this alone, unless you know
# what most of your IMAP clients are. Caching more fields than needed makes
# the index files larger and generate useless I/O.
#
# With maildir there's one extra optimization - if nothing is cached, indexing
# the maildir becomes much faster since it's not opening any of the mail files.
# This could be useful if your IMAP clients access only new mails.
#mail_cache_fields = MessagePart
# Space-separated list of fields that Dovecot should never set to be cached.
# Useful if you want to save disk space at the cost of more I/O when the fields
# needed.
#mail_never_cache_fields =
# Workarounds for various client bugs:
# oe6-fetch-no-newmail:
# Never send EXISTS/RECENT when replying to FETCH command. Outlook Express
# seems to think they are FETCH replies and gives user "Message no longer
# in server" error. Note that OE6 still breaks even with this workaround
# if synchronization is set to "Headers Only".
# oe6-fetch-redundant-msgset:
# If client requests "nextuid:*" messageset, don't return the last message
# as RFC3501 would require. This may considerably improve Dovecot's caching
# decisions for OE6 users.
# outlook-idle:
# Outlook and Outlook Express never abort IDLE command, so if no mail
# arrives in half a hour, Dovecot closes the connection. This is still
# fine, except Outlook doesn't connect back so you don't see if new mail
# arrives.
#client_workarounds =
# Dovecot can notify client of new mail in selected mailbox soon after it's
# received. This setting specifies the minimum interval in seconds between
# new mail notifications to client - internally they may be checked more or
# less often. Setting this to 0 disables the checking.
# NOTE: Evolution client breaks with this option when it's trying to APPEND.
#mailbox_check_interval = 0
# Like mailbox_check_interval, but used for IDLE command.
#mailbox_idle_check_interval = 30
# Allow full filesystem access to clients. There's no access checks other than
# what the operating system does for the active UID/GID. It works with both
# maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/
# or ~user/.
#mail_full_filesystem_access = no
# Maximum allowed length for mail keyword name. It's only forced when trying
# to create new keywords.
#mail_max_keyword_length = 50
# Save mails with CR+LF instead of plain LF. This makes sending those mails
# take less CPU, especially with sendfile() syscall with Linux and FreeBSD.
# But it also creates a bit more disk I/O which may just make it slower.
#mail_save_crlf = no
# Use mmap() instead of read() to read mail files. read() seems to be a bit
# faster with my Linux/x86 and it's better with NFS, so that's the default.
# Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes.
#mail_read_mmaped = no
# Don't use mmap() at all. This is required if you store indexes in remote
# filesystems (NFS or clustered filesystem).
#mmap_disable = no
# Don't write() to mmaped files. This is required for some operating systems
# which use separate caches for them, such as OpenBSD.
#mmap_no_write = no
# Don't use fcntl() locking. Alternatives are dotlocking and other tricks
# which may be slower. Required for NFS.
#fcntl_locks_disable = no
# Copy mail to another folders using hard links. This is much faster than
# actually copying the file. This is problematic only if something modifies
# the mail in one folder but doesn't want it modified in the others. I don't
# know any MUA which would modify mail files directly. IMAP protocol also
# requires that the mails don't change, so it would be problematic in any case.
# If you care about performance, enable it.
#maildir_copy_with_hardlinks = no
# Check if mails' content has been changed by external programs. This slows
# down things as extra stat() needs to be called for each file. If changes are
# noticed, the message is treated as a new message, since IMAP protocol
# specifies that existing messages are immutable.
#maildir_check_content_changes = no
# Which locking methods to use for locking mbox. There's three available:
# dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe
# solution. If you want to use /var/mail/ like directory, the users
# will need write access to that directory.
# fcntl : Use this if possible. Works with NFS too if lockd is used.
# flock : May not exist in all systems. Doesn't work with NFS.
#
# You can use both fcntl and flock too; if you do the order they're declared
# with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl
# and flock. Some operating systems don't allow using both of them
# simultaneously, eg. BSDs. If dotlock is used, it's always created first.
#mbox_locks = dotlock fcntl
# Should we create dotlock file even when we want only a read-lock? Setting
# this to yes hurts the performance when the mailbox is accessed simultaneously
# by multiple processes, but it's needed for reliable reading if no other
# locking methods are available.
#mbox_read_dotlock = no
# Maximum time in seconds to wait for lock (all of them) before aborting.
#mbox_lock_timeout = 300
# If dotlock exists but the mailbox isn't modified in any way, override the
# lock file after this many seconds.
#mbox_dotlock_change_timeout = 30
# umask to use for mail files and directories
#umask = 0077
# Drop all privileges before exec()ing the mail process. This is mostly
# meant for debugging, otherwise you don't get core dumps. Note that setting
# this to yes means that log file is opened as the logged in user, which
# might not work. It could also be a small security risk if you use single UID
# for multiple users, as the users could ptrace() each others processes then.
#mail_drop_priv_before_exec = no
# Set max. process size in megabytes. Most of the memory goes to mmap()ing
# files, so it shouldn't harm much even if this limit is set pretty high.
#mail_process_size = 256
##
## IMAP specific settings
##
protocol imap {
# Login executable location.
#login_executable = /usr/libexec/dovecot/imap-login
# IMAP executable location
#mail_executable = /usr/libexec/dovecot/imap
# This would write rawlogs into ~/dovecot.rawlog/ directory:
#mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap
# Maximum IMAP command line length in bytes. Some clients generate very long
# command lines with huge mailboxes, so you may need to raise this if you get
# "Too long argument" or "IMAP command line too large" errors often.
#imap_max_line_length = 65536
# Support for dynamically loadable modules.
#mail_use_modules = no
#mail_modules = /usr/lib/dovecot/imap
}
##
## POP3 specific settings
##
protocol pop3 {
# Login executable location.
#login_executable = /usr/libexec/dovecot/pop3-login
# POP3 executable location
#mail_executable = /usr/libexec/dovecot/pop3
# Support for dynamically loadable modules.
#mail_use_modules = no
#mail_modules = /usr/lib/dovecot/pop3
}
##
## Authentication processes
##
# You can have multiple authentication processes. With plaintext authentication
# the password is checked against each process, the first one which succeeds is
# used. This is useful if you want to allow both system users (/etc/passwd)
# and virtual users to login without duplicating the system users into virtual
# database.
# Executable location
#auth_executable = /usr/libexec/dovecot/dovecot-auth
# Set max. process size in megabytes.
#auth_process_size = 256
# Space separated list of realms for SASL authentication mechanisms that need
# them. You can leave it empty if you don't want to support multiple realms.
# Many clients simply use the first one listed here, so keep the default realm
# first.
#auth_realms =
# Default realm to use if none was specified.
#auth_default_realm =
# List of allowed characters in username. If the user-given username contains
# a character not listed in here, the login automatically fails. This is just
# an extra check to make sure user can't exploit any potential quote escaping
# vulnerabilities with SQL/LDAP databases. If you want to allow all characters,
# set this value to empty.
#auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
# Username to use for users logging in with ANONYMOUS SASL mechanism
#auth_anonymous_username = anonymous
# More verbose logging. Useful for figuring out why authentication isn't
# working.
#auth_verbose = no
auth default {
# Space separated list of wanted authentication mechanisms:
# plain digest-md5 cram-md5 anonymous
mechanisms = plain
# Where user database is kept:
# passwd: /etc/passwd or similiar, using getpwnam()
# passwd-file <path>: passwd-like file with specified location
# static uid=<uid> gid=<gid> home=<dir template>: static settings
# vpopmail: vpopmail library
# ldap <config path>: LDAP, see doc/dovecot-ldap.conf
# pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf
userdb = passwd
# Where password database is kept:
# passwd: /etc/passwd or similiar, using getpwnam()
# shadow: /etc/shadow or similiar, using getspnam()
# pam [<service> | *]: PAM authentication
# passwd-file <path>: passwd-like file with specified location
# vpopmail: vpopmail authentication
# ldap <config path>: LDAP, see doc/dovecot-ldap.conf
# pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf
passdb = pam
# User to use for the process. This user needs access to only user and
# password databases, nothing else. Only shadow and pam authentication
# requires roots, so use something else if possible. Note that passwd
# authentication with BSDs internally accesses shadow files, which also
# requires roots.
user = root
# Directory where to chroot the process. Most authentication backends don't
# work if this is set, and there's no point chrooting if auth_user is root.
#chroot =
# Number of authentication processes to create
#count = 1
}
# PAM doesn't provide a way to get uid, gid or home directory. If you don't
# want to use a separate user database (passwd usually), you can use static
# userdb.
#auth onlypam {
# mechanisms = plain
# userdb = static uid=500 gid=500 home=/var/mail/%u
# passdb = pam
# user = dovecot-auth
#}
#auth ldap {
# mechanisms = plain
# userdb = ldap /etc/dovecot-ldap.conf
# passdb = ldap /etc/dovecot-ldap.conf
# user = dovecot-auth
#}
#auth virtualfile {
# mechanisms = plain digest-md5
# userdb = passwd-file /etc/passwd.imap
# passdb = passwd-file /etc/passwd.imap
# user = dovecot-auth
#}