text:
#1 Le 07/01/2013, à 19:38
- PounkyM
Installation de dovecot
Bonjour à tous,
Dans le but d'installer un serveur mail, j'ai essayé de suivre ce tuto mais au moment d'installer dovecot, j'ai eu quelques soucis :
% sudo /etc/init.d/dovecot restart
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:837: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:875: passdb pam {} has been replaced by passdb { driver=pam }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:987: userdb passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1049: auth_user has been replaced by service auth { user }
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_cert not set
[....] Restarting IMAP/POP3 mail server: dovecotdoveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:837: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:875: passdb pam {} has been replaced by passdb { driver=pam }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:987: userdb passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1049: auth_user has been replaced by service auth { user }
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl enabled, but ssl_cert not set
Pouvez-vous m'aider pour résoudre ce problème ?
Merci d'avance !
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#2 Le 07/01/2013, à 21:39
- src
Re : Installation de dovecot
Bizarre, le tuto ne détaille pas de configuration particulière pour dovecot, donc peu de chances de leur mettre en vrac !
Or là on dirait que c'est le cas.
Tu es sur quel OS ?
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#3 Le 07/01/2013, à 21:41
- PounkyM
Re : Installation de dovecot
Sur une debian…
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#4 Le 07/01/2013, à 21:44
- src
Re : Installation de dovecot
Tu as fait un upgrade d'une version majeure à une autre ?
Tu as ajouté un dépôt particulier pour avoir dovecot ?
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#5 Le 07/01/2013, à 21:46
- PounkyM
Re : Installation de dovecot
Je crois que j'ai juste fait :
sudo apt-get install dovecot
Mais quand je l'ai installé, c'était bizarre, il n'y avait pas ce fichier dans mon /etc/dovecot par exemple…
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#6 Le 07/01/2013, à 21:50
- src
Re : Installation de dovecot
Au temps pour moi j'ai zappé une partie du tuto.
Bon tout ce qui est en warning ce sont des avertissements sur le fait que certains paramètres sont obsolètes, mais normalement ça n'est pas trop grave.
Je crois que ça bloque parce que tu demande explicitement à dovecot de n'accepter que les connexions chiffrées (ssl)
Or tu n'as pas défini de clé et certificat
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#7 Le 07/01/2013, à 21:59
- PounkyM
Re : Installation de dovecot
Pourtant tout est commenté dans mon dovecot.conf (sauf ce qui est demandé d'être décommenté dans le tuto)…
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#8 Le 07/01/2013, à 22:01
- src
Re : Installation de dovecot
Peux-tu trouver les lignes suivantes dans ton dovecot.conf :
ssl_cert =
ssl_key =
Ces lignes doivent contenir des références à deux fichiers pem, il faut vérifier si ils existent.
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#9 Le 07/01/2013, à 22:04
- PounkyM
Re : Installation de dovecot
Voici les lignes que j'ai trouvé :
#ssl_cert_file = /etc/ssl/certs/dovecot.pem
#ssl_cert_username_field = commonName
#ssl_key_file = /etc/ssl/private/dovecot.pem
#ssl_key_password =
Mais d'après un forum sur debian la solution serait :
Looks like you previously had a dovecot 1.x install that was removed leaving it's config file.
Wheezy uses dovecot 2.x and some of the parameters have changed, as described in the error message.
You need to configure the dovecot.conf file to how you want it to work.
Check the docs in /usr/share/docs/dovecot* and at dovecot.org
Ne serait-il pas plus simple que je désinstalle tout et réinstalle un dovecot 2.x ?
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#10 Le 07/01/2013, à 22:31
- src
Re : Installation de dovecot
D'où ma question au début de savoir si tu as fait un upgrade...
Debian Squeeze utilise une version 1.x de dovecot alors que Wheezy (et ubuntu server) sont sur la 2.x
Une différence notable est que les fichiers de configuration sont maintenant découpés en plusieurs parties, ce que je trouve personnellement plus explicite.
Commence par décommenter (retirer le #) les deux lignes :
#ssl_cert_file = /etc/ssl/certs/dovecot.pem
#ssl_key_file = /etc/ssl/private/dovecot.pem
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#11 Le 07/01/2013, à 22:34
- PounkyM
Re : Installation de dovecot
Oui, j'ai fait un upgrade vers wheezy…
J'ai décommenté les deux lignes, mais je crois que j'ai toujours les mêmes erreurs :
% sudo /etc/init.d/dovecot restart
doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:95: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:96: ssl_key_file has been replaced by ssl_key = <file
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:837: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:875: passdb pam {} has been replaced by passdb { driver=pam }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:987: userdb passwd {} has been replaced by userdb { driver=passwd }
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1049: auth_user has been replaced by service auth { user }
[....] Restarting IMAP/POP3 mail server: dovecotdoveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:95: ssl_cert_file has been replaced by ssl_cert = <file
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 95: ssl_cert: Can't open file /etc/ssl/certs/dovecot.pem: No such file or directory
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#12 Le 07/01/2013, à 22:45
- src
Re : Installation de dovecot
Essaie :
# apt-get install ca-certificates
Dernière modification par src (Le 07/01/2013, à 22:45)
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#13 Le 07/01/2013, à 22:46
- PounkyM
Re : Installation de dovecot
J'ai l'impression que je n'ai pas ce paquet…
% sudo apt-get install ca-cert
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ca-cert
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#14 Le 07/01/2013, à 22:49
- src
Re : Installation de dovecot
J'ai l'impression que je n'ai pas ce paquet…
% sudo apt-get install ca-cert Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ca-cert
Oui désolé, erreur de ma part, j'ai corrigé le nom du paquet.
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#15 Le 07/01/2013, à 22:52
- PounkyM
Re : Installation de dovecot
Le paquet semble déjà installé…
% sudo apt-get install ca-certificates
Reading package lists... Done
Building dependency tree
Reading state information... Done
ca-certificates is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 57 not upgraded
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#16 Le 07/01/2013, à 22:54
- src
Re : Installation de dovecot
/etc/ssl/certs/dovecot.pem existe bien ?
EDIT : Tu peux essayer cette syntaxe :
ssl_cert = </etc/ssl/certs/dovecot.pem
ssl_key = </etc/ssl/private/dovecot.pem
Dernière modification par src (Le 07/01/2013, à 22:55)
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#17 Le 07/01/2013, à 22:57
- PounkyM
Re : Installation de dovecot
Non, le fichier dovecot.pem n'existe pas !
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#18 Le 07/01/2013, à 22:59
- src
Re : Installation de dovecot
Peut-être avec un :
dpkg-reconfigure dovecot-imapd
Sinon tu peux aussi tenter :
# find / -name "dovecot.pem" -print
(Ce qui permet de localiser ce fichier, si il existe)
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#19 Le 07/01/2013, à 23:36
- PounkyM
Re : Installation de dovecot
Pour dpkg-reconfigure, j'ai eu un problème :
% dpkg-reconfigure dovecot-imapd
zsh: command not found: dpkg-reconfigure
Alors, j'ai voulu l'installer mais…
% sudo apt-get install dpkg-reconfigure
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dpkg-reconfigure
Quand au dovecot.pem, voici ce que find a trouvé :
% sudo find / -name "dovecot.pem" -print
Je les déplace dans /etc/ssl/certs ?
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#20 Le 08/01/2013, à 18:40
- PounkyM
Re : Installation de dovecot
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#21 Le 08/01/2013, à 21:17
- src
Re : Installation de dovecot
Non le mieux serait d'éditer ton dovecot.conf comme ceci :
ssl_cert = </etc/dovecot/dovecot.pem
ssl_key = </etc/dovecot/private/dovecot.pem
Actuellement sur Manjaro Xfce (amd64)
Serveur sur Debian Jessie (i386) + LXC
Hors ligne
#22 Le 08/01/2013, à 22:00
- sylvain1970
Re : Installation de dovecot
est-il possible d'avoir le fichier dovecot.conf en entier ? (après avoir mis des xxxxx sur tout login ou pass) ?
Dernière modification par sylvain1970 (Le 08/01/2013, à 22:00)
Hors ligne
#23 Le 08/01/2013, à 22:27
- PounkyM
Re : Installation de dovecot
@src : c'est ssl_cert_file et ssl_key_file plutôt non ?
@sylvain : j'aimerais bien mais je n'arrive pas… (quand je le cat dans le terminal, je ne peux pas remonter assez haut pour le copier et le coller ici… mais de toute manière, tout est commenté…)
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne
#24 Le 08/01/2013, à 22:51
- sylvain1970
Re : Installation de dovecot
tu peux faire un :
cat /etc/dovecot/dovecot.conf | more
pour que çà affiche par page le fichier (barre espace pour passer à la page suivante).
Dovecot va gérer l'authentification (sur le tuto que tu as suivi, la partie Login... Passwd... ), il lui faut un minimum de configuration.
Dernière modification par sylvain1970 (Le 08/01/2013, à 23:03)
Hors ligne
#25 Le 09/01/2013, à 16:07
- PounkyM
Re : Installation de dovecot
% cat /etc/dovecot/dovecot.conf | more
## Dovecot configuration file
# If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration
# "dovecot -n" command gives a clean output of the changed settings. Use it
# instead of copy&pasting this file when posting to the Dovecot mailing list.
# '#' character and everything after it is treated as comments. Extra spaces
# and tabs are ignored. If you want to use either of these explicitly, put the
# value inside quotes, eg.: key = "# char and trailing whitespace "
# Default values are shown for each setting, it's not required to uncomment
# those. These are exceptions to this though: No sections (e.g. namespace {})
# or plugin settings are added by default, they're listed only as examples.
# Paths are also just examples with the real defaults being based on configure
# options. The paths listed here are for configure --prefix=/usr
# --sysconfdir=/etc --localstatedir=/var --with-ssldir=/etc/ssl
# Base directory where to store runtime data.
#base_dir = /var/run/dovecot/
# Protocols we want to be serving: imap imaps pop3 pop3s
# If you only want to use dovecot-auth, you can set this to "none".
#protocols = imap imaps
# A space separated list of IP or host addresses where to listen in for
# connections. "*" listens in all IPv4 interfaces. "[::]" listens in all IPv6
# interfaces. Use "*, [::]" for listening both IPv4 and IPv6.
# If you want to specify ports for each service, you will need to configure
# these settings inside the protocol imap/pop3 { ... } section, so you can
# specify different ports for IMAP/POP3. For example:
# protocol imap {
# listen = *:10143
# ssl_listen = *:10943
# ..
# }
# protocol pop3 {
# listen = *:10100
# ..
# }
#listen = *
# Disable LOGIN command and all other plaintext authentications unless
# SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP
# matches the local IP (ie. you're connecting from the same computer), the
# connection is considered secure and plaintext authentication is allowed.
#disable_plaintext_auth = yes
# Should all IMAP and POP3 processes be killed when Dovecot master process
# shuts down. Setting this to "no" means that Dovecot can be upgraded without
# forcing existing client connections to close (although that could also be
# a problem if the upgrade is eg. because of a security fix). This however
# means that after master process has died, the client processes can't write
# to log files anymore.
#shutdown_clients = yes
## Logging
# Log file to use for error messages, instead of sending them to syslog.
# /dev/stderr can be used to log into stderr.
#log_path =
# Log file to use for informational and debug messages.
# Default is the same as log_path.
#info_log_path =
# Prefix for each line written to log file. % codes are in strftime(3)
# format.
#log_timestamp = "%b %d %H:%M:%S "
# Syslog facility to use if you're logging to syslog. Usually if you don't
# want to use "mail", you'll use local0..local7. Also other standard
# facilities are supported.
#syslog_facility = mail
## SSL settings
# IP or host address where to listen in for SSL connections. Remember to also
# add imaps and/or pop3s to protocols setting. Defaults to same as "listen"
# setting if not specified.
#ssl_listen =
# SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>
#ssl = yes
# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before
# dropping root privileges, so keep the key file unreadable by anyone but
# root. Included doc/mkcert.sh can be used to easily generate self-signed
# certificate, just make sure to update the domains in dovecot-openssl.cnf
ssl_cert_file = /etc/ssl/certs/dovecot.pem
ssl_key_file = /etc/ssl/private/dovecot.pem
# If key file is password protected, give the password here. Alternatively
# give it when starting dovecot with -p parameter. Since this file is often
# world-readable, you may want to place this setting instead to a different
# root owned 0600 file by using !include_try <path>.
#ssl_key_password =
# File containing trusted SSL certificate authorities. Set this only if you
# intend to use ssl_verify_client_cert=yes. The CAfile should contain the
# CA-certificate(s) followed by the matching CRL(s).
#ssl_ca_file =
# Request client to send a certificate. If you also want to require it, set
# ssl_require_client_cert=yes in auth section.
#ssl_verify_client_cert = no
# Which field from certificate to use for username. commonName and
# x500UniqueIdentifier are the usual choices. You'll also need to set
# ssl_username_from_cert=yes.
#ssl_cert_username_field = commonName
# How often to regenerate the SSL parameters file. Generation is quite CPU
# intensive operation. The value is in hours, 0 disables regeneration
# entirely.
#ssl_parameters_regenerate = 168
# SSL ciphers to use
#ssl_cipher_list = ALL:!LOW:!SSLv2
# Show protocol level SSL errors.
#verbose_ssl = no
## Login processes
# <doc/wiki/LoginProcess.txt>
# Directory where authentication process places authentication UNIX sockets
# which login needs to be able to connect to. The sockets are created when
# running as root, so you don't have to worry about permissions. Note that
# everything in this directory is deleted when Dovecot is started.
#login_dir = /var/run/dovecot/login
# chroot login process to the login_dir. Only reason not to do this is if you
# wish to run the whole Dovecot without roots. <doc/wiki/Rootless.txt>
#login_chroot = yes
# User to use for the login process. Create a completely new user for this,
# and don't use it anywhere else. The user must also belong to a group where
# only it has access, it's used to control access for authentication process.
# Note that this user is NOT used to access mails. <doc/wiki/UserIds.txt>
#login_user = dovecot
# Set max. process size in megabytes. If you don't use
# login_process_per_connection you might need to grow this.
#login_process_size = 64
# Should each login be processed in it's own process (yes), or should one
# login process be allowed to process multiple connections (no)? Yes is more
# secure, espcially with SSL/TLS enabled. No is faster since there's no need
# to create processes all the time.
#login_process_per_connection = yes
# Number of login processes to keep for listening new connections.
#login_processes_count = 3
# Maximum number of login processes to create. The listening process count
# usually stays at login_processes_count, but when multiple users start logging
# in at the same time more extra processes are created. To prevent fork-bombing
# we check only once in a second if new processes should be created - if all
# of them are used at the time, we double their amount until the limit set by
# this setting is reached.
#login_max_processes_count = 128
# Maximum number of connections allowed per each login process. This setting
# is used only if login_process_per_connection=no. Once the limit is reached,
# the process notifies master so that it can create a new login process.
#login_max_connections = 256
# Greeting message for clients.
#login_greeting = Dovecot ready.
# Space separated list of trusted network ranges. Connections from these
# IPs are allowed to override their IP addresses and ports (for logging and
# for authentication checks). disable_plaintext_auth is also ignored for
# these networks. Typically you'd specify your IMAP proxy servers here.
#login_trusted_networks =
# Space-separated list of elements we want to log. The elements which have
# a non-empty variable value are joined together to form a comma-separated
# string.
#login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
# Login log format. %$ contains login_log_format_elements string, %s contains
# the data we want to log.
#login_log_format = %$: %s
## Mailbox locations and namespaces
# Location for users' mailboxes. This is the same as the old default_mail_env
# setting. The default is empty, which means that Dovecot tries to find the
# mailboxes automatically. This won't work if the user doesn't have any mail
# yet, so you should explicitly tell Dovecot the full location.
# If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u)
# isn't enough. You'll also need to tell Dovecot where the other mailboxes are
# kept. This is called the "root mail directory", and it must be the first
# path given in the mail_location setting.
# There are a few special variables you can use, eg.:
# %u - username
# %n - user part in user@domain, same as %u if there's no domain
# %d - domain part in user@domain, empty if there's no domain
# %h - home directory
# See <doc/wiki/Variables.txt> for full list. Some examples:
# mail_location = maildir:~/Maildir
# mail_location = mbox:~/mail:INBOX=/var/mail/%u
# mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n
# <doc/wiki/MailLocation.txt>
#mail_location =
# If you need to set multiple mailbox locations or want to change default
# namespace settings, you can do it by defining namespace sections.
# You can have private, shared and public namespaces. Private namespaces
# are for user's personal mails. Shared namespaces are for accessing other
# users' mailboxes that have been shared. Public namespaces are for shared
# mailboxes that are managed by sysadmin. If you create any shared or public
# namespaces you'll typically want to enable ACL plugin also, otherwise all
# users can access all the shared mailboxes, assuming they have permissions
# on filesystem level to do so.
# REMEMBER: If you add any namespaces, the default namespace must be added
# explicitly, ie. mail_location does nothing unless you have a namespace
# without a location setting. Default namespace is simply done by having a
# namespace with empty prefix.
#namespace private {
# Hierarchy separator to use. You should use the same separator for all
# namespaces or some clients get confused. '/' is usually a good one.
# The default however depends on the underlying mail storage format.
#separator =
# Prefix required to access this namespace. This needs to be different for
# all namespaces. For example "Public/".
#prefix =
# Physical location of the mailbox. This is in same format as
# mail_location, which is also the default for it.
#location =
# There can be only one INBOX, and this setting defines which namespace
# has it.
#inbox = no
# If namespace is hidden, it's not advertised to clients via NAMESPACE
# extension. You'll most likely also want to set list=no. This is mostly
# useful when converting from another server with different namespaces which
# you want to deprecate but still keep working. For example you can create
# hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/".
#hidden = yes
# Show the mailboxes under this namespace with LIST command. This makes the
# namespace visible for clients that don't support NAMESPACE extension.
# "children" value lists child mailboxes, but hides the namespace prefix.
#list = yes
# Namespace handles its own subscriptions. If set to "no", the parent
# namespace handles them (empty prefix should always have this as "yes")
#subscriptions = yes
# Example shared namespace configuration
#namespace shared {
#separator = /
# Mailboxes are visible under "shared/user@domain/"
# %%n, %%d and %%u are expanded to the destination user.
#prefix = shared/%%u/
# Mail location for other users' mailboxes. Note that %variables and ~/
# expands to the logged in user's data. %%n, %%d, %%u and %%h expand to the
# destination user's data.
#location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u
# Use the default namespace for saving subscriptions.
#subscriptions = no
# List the shared/ namespace only if there are visible shared mailboxes.
#list = children
# System user and group used to access mails. If you use multiple, userdb
# can override these by returning uid or gid fields. You can use either numbers
# or names. <doc/wiki/UserIds.txt>
#mail_uid =
#mail_gid =
# Group to enable temporarily for privileged operations. Currently this is
# used only with INBOX when either its initial creation or dotlocking fails.
# Typically this is set to "mail" to give access to /var/mail.
#mail_privileged_group =
# Grant access to these supplementary groups for mail processes. Typically
# these are used to set up access to shared mailboxes. Note that it may be
# dangerous to set these if users can create symlinks (e.g. if "mail" group is
# set here, ln -s /var/mail ~/mail/var could allow a user to delete others'
# mailboxes, or ln -s /secret/shared/box ~/mail/mybox would allow reading it).
#mail_access_groups =
# 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
## Mail processes
# Enable mail process debugging. This can help you figure out why Dovecot
# isn't finding your mails.
#mail_debug = no
# Log prefix for mail processes. See <doc/wiki/Variables.txt> for list of
# possible variables you can use.
#mail_log_prefix = "%Us(%u): "
# Max. number of lines a mail process is allowed to log per second before it's
# throttled. 0 means unlimited. Typically there's no need to change this
# unless you're using mail_log plugin, which may log a lot. This setting is
# ignored while mail_debug=yes to avoid pointless throttling.
#mail_log_max_lines_per_sec = 10
# Don't use mmap() at all. This is required if you store indexes to shared
# filesystems (NFS or clustered filesystem).
#mmap_disable = no
# Rely on O_EXCL to work when creating dotlock files. NFS supports O_EXCL
# since version 3, so this should be safe to use nowadays by default.
#dotlock_use_excl = yes
# Don't use fsync() or fdatasync() calls. This makes the performance better
# at the cost of potential data loss if the server (or the file server)
# goes down.
#fsync_disable = no
# Mail storage exists in NFS. Set this to yes to make Dovecot flush NFS caches
# whenever needed. If you're using only a single mail server this isn't needed.
#mail_nfs_storage = no
# Mail index files also exist in NFS. Setting this to yes requires
# mmap_disable=yes and fsync_disable=no.
#mail_nfs_index = no
# Locking method for index files. Alternatives are fcntl, flock and dotlock.
# Dotlocking uses some tricks which may create more disk I/O than other locking
# methods. NFS users: flock doesn't work, remember to change mmap_disable.
#lock_method = fcntl
# Drop all privileges before exec()ing the mail process. This is mostly
# meant for debugging, otherwise you don't get core dumps. It could 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
# Show more verbose process titles (in ps). Currently shows user name and
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = 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
# Maximum number of running mail processes. When this limit is reached,
# new users aren't allowed to log in.
#max_mail_processes = 512
# 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
# Maximum allowed length for mail keyword name. It's only forced when trying
# to create new keywords.
#mail_max_keyword_length = 50
# ':' 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, mail_chroot or auth chroot
# settings. If this setting is empty, "/./" in home dirs are ignored.
# 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. <doc/wiki/Chrooting.txt>
#valid_chroot_dirs =
# Default chroot directory for mail processes. This can be overridden for
# specific users in user database by giving /./ in user's home directory
# (eg. /home/./user chroots into /home). Note that usually there is no real
# need to do chrooting, Dovecot doesn't allow users to access files outside
# their mail directory anyway. If your home directories are prefixed with
# the chroot directory, append "/." to mail_chroot. <doc/wiki/Chrooting.txt>
#mail_chroot =
## Mailbox handling optimizations
# The minimum number of mails in a mailbox before updates are done to cache
# file. This allows optimizing Dovecot's behavior to do less disk writes at
# the cost of more disk reads.
#mail_cache_min_mail_count = 0
# When IDLE command is running, mailbox is checked once in a while to see if
# there are any new mails or other changes. This setting defines the minimum
# time in seconds to wait between those checks. Dovecot can also use dnotify,
# inotify and kqueue to find out immediately when changes occur.
#mailbox_idle_check_interval = 30
# 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.
# Also note that if other software reads the mboxes/maildirs, they may handle
# the extra CRs wrong and cause problems.
#mail_save_crlf = no
## Maildir-specific settings
# By default LIST command returns all entries in maildir beginning with a dot.
# Enabling this option makes Dovecot return only entries which are directories.
# This is done by stat()ing each entry, so it causes more disk I/O.
# (For systems setting struct dirent->d_type, this check is free and it's
# done always regardless of this setting)
#maildir_stat_dirs = no
# When copying a message, do it with hard links whenever possible. This makes
# the performance much better, and it's unlikely to have any side effects.
#maildir_copy_with_hardlinks = yes
# When copying a message, try to preserve the base filename. Only if the
# destination mailbox already contains the same name (ie. the mail is being
# copied there twice), a new name is given. The destination filename check is
# done only by looking at dovecot-uidlist file, so if something outside
# Dovecot does similar filename preserving copies, you may run into problems.
# NOTE: This setting requires maildir_copy_with_hardlinks = yes to work.
#maildir_copy_preserve_filename = no
# Assume Dovecot is the only MUA accessing Maildir: Scan cur/ directory only
# when its mtime changes unexpectedly or when we can't find the mail otherwise.
#maildir_very_dirty_syncs = no
## mbox-specific settings
# Which locking methods to use for locking mbox. There are four 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.
# dotlock_try: Same as dotlock, but if it fails because of permissions or
# because there isn't enough disk space, just skip it.
# 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.
# lockf : May not exist in all systems. Doesn't work with NFS.
# You can use multiple locking methods; if you do the order they're declared
# in is important to avoid deadlocks if other MTAs/MUAs are using multiple
# locking methods as well. Some operating systems don't allow using some of
# them simultaneously.
#mbox_read_locks = fcntl
#mbox_write_locks = dotlock fcntl
# 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 = 120
# When mbox changes unexpectedly we have to fully read it to find out what
# changed. If the mbox is large this can take a long time. Since the change
# is usually just a newly appended mail, it'd be faster to simply read the
# new mails. If this setting is enabled, Dovecot does this but still safely
# fallbacks to re-reading the whole mbox file whenever something in mbox isn't
# how it's expected to be. The only real downside to this setting is that if
# some other MUA changes message flags, Dovecot doesn't notice it immediately.
# Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK
# commands.
#mbox_dirty_syncs = yes
# Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE,
# EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored.
#mbox_very_dirty_syncs = no
# Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK
# commands and when closing the mailbox). This is especially useful for POP3
# where clients often delete all mails. The downside is that our changes
# aren't immediately visible to other MUAs.
#mbox_lazy_writes = yes
# If mbox size is smaller than this (in kilobytes), don't write index files.
# If an index file already exists it's still read, just not updated.
#mbox_min_index_size = 0
## dbox-specific settings
# Maximum dbox file size in kilobytes until it's rotated.
#dbox_rotate_size = 2048
# Minimum dbox file size in kilobytes before it's rotated
# (overrides dbox_rotate_days)
#dbox_rotate_min_size = 16
# Maximum dbox file age in days until it's rotated. Day always begins from
# midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled.
#dbox_rotate_days = 0
## IMAP specific settings
protocol imap {
# Login executable location.
#login_executable = /usr/libexec/dovecot/imap-login
# IMAP executable location. Changing this allows you to execute other
# binaries before the imap process is executed.
# This would write rawlogs into user's ~/dovecot.rawlog/, if it exists:
# mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap
# <doc/wiki/Debugging/Rawlog.txt>
# This would attach gdb into the imap process and write backtraces into
# /tmp/gdbhelper.* files:
# mail_executable = /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap
#mail_executable = /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
# Maximum number of IMAP connections allowed for a user from each IP address.
# NOTE: The username is compared case-sensitively.
#mail_max_userip_connections = 10
# Support for dynamically loadable plugins. mail_plugins is a space separated
# list of plugins to load.
#mail_plugins =
#mail_plugin_dir = /usr/lib/dovecot/lda
# If user is over quota, return with temporary failure instead of
# bouncing the mail.
#quota_full_tempfail = no
# Format to use for logging mail deliveries. You can use variables:
# %$ - Delivery status message (e.g. "saved to INBOX")
# %m - Message-ID
# %s - Subject
# %f - From address
#deliver_log_format = msgid=%m: %$
# Binary to use for sending mails.
#sendmail_path = /usr/lib/sendmail
# Subject: header to use for rejection mails. You can use the same variables
# as for rejection_reason below.
#rejection_subject = Rejected: %s
# Human readable error message for rejection mails. You can use variables:
# %n = CRLF, %r = reason, %s = original subject, %t = recipient
#rejection_reason = Your message to <%t> was automatically rejected:%n%r
# UNIX socket path to master authentication server to find users.
#auth_socket_path = /var/run/dovecot/auth-master
## Authentication processes
# Executable location
#auth_executable = /usr/libexec/dovecot/dovecot-auth
# Set max. process size in megabytes.
#auth_process_size = 256
# Authentication cache size in kilobytes. 0 means it's disabled.
# Note that bsdauth, PAM and vpopmail require cache_key to be set for caching
# to be used.
#auth_cache_size = 0
# Time to live in seconds for cached data. After this many seconds the cached
# record is no longer used, *except* if the main database lookup returns
# internal failure. We also try to handle password changes automatically: If
# user's previous authentication was successful, but this one wasn't, the
# cache isn't used. For now this works only with plaintext authentication.
#auth_cache_ttl = 3600
# TTL for negative hits (user not found, password mismatch).
# 0 disables caching them completely.
#auth_cache_negative_ttl = 3600
# 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/domain to use if none was specified. This is used for both
# SASL realms and appending @domain to username in plaintext logins.
#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 character translations before it's looked up from databases. The
# value contains series of from -> to characters. For example "#@/@" means
# that '#' and '/' characters are translated to '@'.
#auth_username_translation =
# Username formatting before it's looked up from databases. You can use
# the standard variables here, eg. %Lu would lowercase the username, %n would
# drop away the domain if it was given, or "%n-AT-%d" would change the '@' into
# "-AT-". This translation is done after auth_username_translation changes.
#auth_username_format =
# If you want to allow master users to log in by specifying the master
# username within the normal username string (ie. not using SASL mechanism's
# support for it), you can specify the separator character here. The format
# is then <username><separator><master username>. UW-IMAP uses "*" as the
# separator, so that could be a good choice.
#auth_master_user_separator =
# Username to use for users logging in with ANONYMOUS SASL mechanism
#auth_anonymous_username = anonymous
# Log unsuccessful authentication attempts and the reasons why they failed.
#auth_verbose = no
# Even more verbose logging for debugging purposes. Shows for example SQL
# queries.
#auth_debug = no
# In case of password mismatches, log the passwords and used scheme so the
# problem can be debugged. Enabling this also enables auth_debug.
#auth_debug_passwords = no
# Maximum number of dovecot-auth worker processes. They're used to execute
# blocking passdb and userdb queries (eg. MySQL and PAM). They're
# automatically created and destroyed as needed.
#auth_worker_max_count = 30
# Host name to use in GSSAPI principal names. The default is to use the
# name returned by gethostname(). Use "$ALL" to allow all keytab entries.
#auth_gssapi_hostname =
# Kerberos keytab to use for the GSSAPI mechanism. Will use the system
# default (usually /etc/krb5.keytab) if not specified.
#auth_krb5_keytab =
# Do NTLM and GSS-SPNEGO authentication using Samba's winbind daemon and
# ntlm_auth helper. <doc/wiki/Authentication/Mechanisms/Winbind.txt>
#auth_use_winbind = no
# Path for Samba's ntlm_auth helper binary.
#auth_winbind_helper_path = /usr/bin/ntlm_auth
# Number of seconds to delay before replying to failed authentications.
#auth_failure_delay = 2
auth default {
# Space separated list of wanted authentication mechanisms:
# plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi otp skey
# gss-spnego
# NOTE: See also disable_plaintext_auth setting.
mechanisms = plain
# Password database is used to verify user's password (and nothing more).
# You can have multiple passdbs and userdbs. 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.
# <doc/wiki/PasswordDatabase.txt>
# By adding master=yes setting inside a passdb you make the passdb a list
# of "master users", who can log in as anyone else. Unless you're using PAM,
# you probably still want the destination user to be looked up from passdb
# that it really exists. This can be done by adding pass=yes setting to the
# master passdb. <doc/wiki/Authentication.MasterUsers.txt>
# Users can be temporarily disabled by adding a passdb with deny=yes.
# If the user is found from that database, authentication will fail.
# The deny passdb should always be specified before others, so it gets
# checked first. Here's an example:
#passdb passwd-file {
# File contains a list of usernames, one per line
#args = /etc/dovecot.deny
#deny = yes
# PAM authentication. Preferred nowadays by most systems.
# Note that PAM can only be used to verify if user's password is correct,
# so it can't be used as userdb. If you don't want to use a separate user
# database (passwd usually), you can use static userdb.
# REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM
# authentication to actually work. <doc/wiki/PasswordDatabase.PAM.txt>
passdb pam {
# [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=<n>]
# [cache_key=<key>] [<service name>]
# session=yes makes Dovecot open and immediately close PAM session. Some
# PAM plugins need this to work, such as pam_mkhomedir.
# setcred=yes makes Dovecot establish PAM credentials if some PAM plugins
# need that. They aren't ever deleted though, so this isn't enabled by
# default.
# max_requests specifies how many PAM lookups to do in one process before
# recreating the process. The default is 100, because many PAM plugins
# leak memory.
# cache_key can be used to enable authentication caching for PAM
# (auth_cache_size also needs to be set). It isn't enabled by default
# because PAM modules can do all kinds of checks besides checking password,
# such as checking IP address. Dovecot can't know about these checks
# without some help. cache_key is simply a list of variables (see
# doc/wiki/Variables.txt) which must match for the cached data to be used.
# Here are some examples:
# %u - Username must match. Probably sufficient for most uses.
# %u%r - Username and remote IP address must match.
# %u%s - Username and service (ie. IMAP, POP3) must match.
# The service name can contain variables, for example %Ls expands to
# pop3 or imap.
# Some examples:
# args = session=yes %Ls
# args = cache_key=%u dovecot
#args = dovecot
# System users (NSS, /etc/passwd, or similiar)
# In many systems nowadays this uses Name Service Switch, which is
# configured in /etc/nsswitch.conf. <doc/wiki/AuthDatabase.Passwd.txt>
#passdb passwd {
# [blocking=yes] - See userdb passwd for explanation
#args =
# Shadow passwords for system users (NSS, /etc/shadow or similiar).
# Deprecated by PAM nowadays.
# <doc/wiki/PasswordDatabase.Shadow.txt>
#passdb shadow {
# [blocking=yes] - See userdb passwd for explanation
#args =
# PAM-like authentication for OpenBSD.
# <doc/wiki/PasswordDatabase.BSDAuth.txt>
#passdb bsdauth {
# [cache_key=<key>] - See cache_key in PAM for explanation.
#args =
# passwd-like file with specified location
# <doc/wiki/AuthDatabase.PasswdFile.txt>
#passdb passwd-file {
# [scheme=<default password scheme>] [username_format=<format>]
# <Path for passwd-file>
#args =
# checkpassword executable authentication
# NOTE: You will probably want to use "userdb prefetch" with this.
# <doc/wiki/AuthDatabase.CheckPassword.txt>
#passdb checkpassword {
# Path for checkpassword binary
#args =
# SQL database <doc/wiki/AuthDatabase.SQL.txt>
#passdb sql {
# Path for SQL configuration file, see doc/dovecot-sql-example.conf
#args =
# LDAP database <doc/wiki/AuthDatabase.LDAP.txt>
#passdb ldap {
# Path for LDAP configuration file, see doc/dovecot-ldap-example.conf
#args =
# vpopmail authentication <doc/wiki/AuthDatabase.VPopMail.txt>
#passdb vpopmail {
# [cache_key=<key>] - See cache_key in PAM for explanation.
# [quota_template=<template>] - %q expands to Maildir++ quota
# (eg. quota_template=quota_rule=*:backend=%q)
#args =
# User database specifies where mails are located and what user/group IDs
# own them. For single-UID configuration use "static".
# <doc/wiki/UserDatabase.txt>
# "prefetch" user database means that the passdb already provided the
# needed information and there's no need to do a separate userdb lookup.
# This can be made to work with SQL and LDAP databases, see their example
# configuration files for more information how to do it.
# <doc/wiki/UserDatabase.Prefetch.txt>
#userdb prefetch {
# System users (NSS, /etc/passwd, or similiar). In many systems nowadays this
# uses Name Service Switch, which is configured in /etc/nsswitch.conf.
# <doc/wiki/AuthDatabase.Passwd.txt>
userdb passwd {
# [blocking=yes] - By default the lookups are done in the main dovecot-auth
# process. This setting causes the lookups to be done in auth worker
# proceses. Useful with remote NSS lookups that may block.
# NOTE: Be sure to use this setting with nss_ldap or users might get
# logged in as each others!
#args =
# passwd-like file with specified location
# <doc/wiki/AuthDatabase.PasswdFile.txt>
#userdb passwd-file {
# [username_format=<format>] <Path for passwd-file>
#args =
# checkpassword executable user database lookup
# <doc/wiki/AuthDatabase.CheckPassword.txt>
#userdb checkpassword {
# Path for checkpassword binary
#args =
# static settings generated from template <doc/wiki/UserDatabase.Static.txt>
#userdb static {
# Template for the fields. Can return anything a userdb could normally
# return. For example:
# args = uid=500 gid=500 home=/var/mail/%u
# If you use deliver, it needs to look up users only from the userdb. This
# of course doesn't work with static because there is no list of users.
# Normally static userdb handles this by doing a passdb lookup. This works
# with most passdbs, with PAM being the most notable exception. If you do
# the user verification another way, you can add allow_all_users=yes to
# the args in which case the passdb lookup is skipped.
#args =
# SQL database <doc/wiki/AuthDatabase.SQL.txt>
#userdb sql {
# Path for SQL configuration file, see doc/dovecot-sql-example.conf
#args =
# LDAP database <doc/wiki/AuthDatabase.LDAP.txt>
#userdb ldap {
# Path for LDAP configuration file, see doc/dovecot-ldap-example.conf
#args =
# vpopmail <doc/wiki/AuthDatabase.VPopMail.txt>
#userdb vpopmail {
# 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. Note that this user is NOT used to access mails.
# That user is specified by userdb above.
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.
# Note that valid_chroot_dirs isn't needed to use this setting.
#chroot =
# Number of authentication processes to create
#count = 1
# Require a valid SSL client certificate or the authentication fails.
#ssl_require_client_cert = no
# Take the username from client's SSL certificate, using
# X509_NAME_get_text_by_NID() which returns the subject's DN's
# CommonName.
#ssl_username_from_cert = no
# It's possible to export the authentication interface to other programs:
socket listen {
#master {
# Master socket provides access to userdb information. It's typically
# used to give Dovecot's local delivery agent access to userdb so it
# can find mailbox locations.
#path = /var/run/dovecot/auth-master
#mode = 0600
# Default user/group is the one who started dovecot-auth (root)
#user =
#group =
client {
# The client socket is generally safe to export to everyone. Typical use
# is to export it to your SMTP server so it can do SMTP AUTH lookups
# using it.
#path = /var/run/dovecot/auth-client
path = /var/spool/postfix/private/auth
mode = 0660
# If you wish to use another authentication server than dovecot-auth, you can
# use connect sockets. They are assumed to be already running, Dovecot's master
# process only tries to connect to them. They don't need any other settings
# than the path for the master socket, as the configuration is done elsewhere.
# Note that the client sockets must exist in the login_dir.
#auth external {
# socket connect {
# master {
# path = /var/run/dovecot/auth-master
# }
# }
## Dictionary server settings
# Dictionary can be used by some plugins to store key=value lists, such as
# quota, expire and acl plugins. The dictionary can be used either directly or
# though a dictionary server. The following dict block maps dictionary names to
# URIs when the server is used. These can then be referenced using URIs in
# format "proxy::<name>".
dict {
#quota = mysql:/etc/dovecot-dict-quota.conf
#expire = db:/var/lib/dovecot/expire.db
# Path to Berkeley DB's configuration file. See doc/dovecot-db-example.conf
#dict_db_config =
## Plugin settings
plugin {
# Here you can give some extra environment variables to mail processes.
# This is mostly meant for passing parameters to plugins. %variable
# expansion is done for all values.
# Quota plugin. Multiple backends are supported:
# dirsize: Find and sum all the files found from mail directory.
# Extremely SLOW with Maildir. It'll eat your CPU and disk I/O.
# dict: Keep quota stored in dictionary (eg. SQL)
# maildir: Maildir++ quota
# fs: Read-only support for filesystem quota
# Quota limits are set using "quota_rule" parameters, either in here or in
# userdb. It's also possible to give mailbox-specific limits, for example:
# quota_rule = *:storage=1048576
# quota_rule2 = Trash:storage=102400
# User has now 1GB quota, but when saving to Trash mailbox the user gets
# additional 100MB.
# Multiple quota roots are also possible, for example:
# quota = dict:user::proxy::quota
# quota2 = dict:domain:%d:proxy::quota_domain
# quota_rule = *:storage=102400
# quota2_rule = *:storage=1048576
# Gives each user their own 100MB quota and one shared 1GB quota within
# the domain.
# You can execute a given command when user exceeds a specified quota limit.
# Each quota root has separate limits. Only the command for the first
# exceeded limit is excecuted, so put the highest limit first.
# Note that % needs to be escaped as %%, otherwise "% " expands to empty.
# quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
# quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80
#quota = maildir
# ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir
# directory. You can also optionally give a global ACL directory path where
# ACLs are applied to all users' mailboxes. The global ACL directory contains
# one file for each mailbox, eg. INBOX or sub.mailbox. cache_secs parameter
# specifies how many seconds to wait between stat()ing dovecot-acl file
# to see if it changed.
#acl = vfile:/etc/dovecot-acls:cache_secs=300
# To let users LIST mailboxes shared by other users, Dovecot needs a
# shared mailbox dictionary. For example:
#acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes
# Convert plugin. If set, specifies the source storage path which is
# converted to destination storage (mail_location) when the user logs in.
# The existing mail directory is renamed to <dir>-converted.
#convert_mail = mbox:%h/mail
# Skip mailboxes which we can't open successfully instead of aborting.
#convert_skip_broken_mailboxes = no
# Skip directories beginning with '.'
#convert_skip_dotdirs = no
# If source storage has mailbox names with destination storage's hierarchy
# separators, replace them with this character.
#convert_alt_hierarchy_char = _
# Trash plugin. When saving a message would make user go over quota, this
# plugin automatically deletes the oldest mails from configured mailboxes
# until the message can be saved within quota limits. The configuration file
# is a text file where each line is in format: <priority> <mailbox name>
# Mails are first deleted in lowest -> highest priority number order
#trash = /etc/dovecot-trash.conf
# Expire plugin. Mails are expunged from mailboxes after being there the
# configurable time. The first expiration date for each mailbox is stored in
# a dictionary so it can be quickly determined which mailboxes contain
# expired mails. The actual expunging is done in a nightly cronjob, which
# you must set up:
# dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool
#expire = Trash 7 Spam 30
#expire_dict = proxy::expire
# Lazy expunge plugin. Currently works only with maildirs. When a user
# expunges mails, the mails are moved to a mailbox in another namespace
# (1st). When a mailbox is deleted, the mailbox is moved to another namespace
# (2nd) as well. Also if the deleted mailbox had any expunged messages,
# they're moved to a 3rd namespace. The mails won't be counted in quota,
# and they're not deleted automatically (use a cronjob or something).
#lazy_expunge = .EXPUNGED/ .DELETED/ .DELETED/.EXPUNGED/
# Events to log. Also available: flag_change append
#mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
# Group events within a transaction to one line.
#mail_log_group_events = no
# Available fields: uid, box, msgid, from, subject, size, vsize, flags
# size and vsize are available only for expunge and copy events.
#mail_log_fields = uid box msgid size
# Config files can also be included. deliver doesn't support them currently.
#!include /etc/dovecot/conf.d/*.conf
# Optional configurations, don't give an error if it's not found:
#!include_try /etc/dovecot/extra.conf
Ça y est je crois que j'ai réussi à le copier/coller!
"La liberté est un bagne aussi longtemps qu'un seul homme est asservi sur la terre"
Hors ligne


text:
Hope and fear mix as hostage situation drags onBy CAMPBELL ROBERTSON
The New York Times | February 03,2013AP Photo
Alabama State Trooper Kevin Cook, center right, is surrounded by the media at a news conference Saturday in Midland City, Ala. Authorities said they still have a line of communication with an Alabama man accused of abducting a 5-year-old child and holding him hostage in a bunker since Tuesday.MIDLAND CITY, Ala. The vigils continued in and around this southeastern Alabama town on Saturday. They were held in private homes, at the gazebo next to City Hall and, perhaps most somberly, on the grassy hill where swarms of federal agents are watching the underground bunker where they say a man named Jimmy Lee Dykes has held a 5-year-old boy hostage for more than four days now.
Law enforcement officials are still saying little about attempts to rescue the boy, who was kidnapped Tuesday when Dykes raided a school bus and killed the driver. Officials have been in constant communication with Dykes through a plastic pipe that he originally installed, a neighbor said, to eavesdrop on trespassers from within the bunker.
The bunker has food and electricity, and Dale County Sheriff Wally Olson said in a news conference Saturday that it also had blankets and an electric heater to get through the near-freezing temperatures at night. He added that toys, coloring books and medication had been passed into the bunker for the boy, who has Aspergers syndrome and attention-deficit hyperactivity disorder.
He did not say if it is known whether the boy has been taking the medicine.
Its one thing when youve got your mother and grandmother giving it to you every day, said state Rep. Steve Clouse, whose district includes Midland City.
Perhaps suggesting that Dykes is following events from his bunker, Olson concluded the short news conference by offering gratitude to Dykes for allowing officials to pass on such necessities.
I want to thank him for taking care of our child, the sheriff said. Its very important.
The Daily Mail of London reported on Saturday that Dykes had initially requested to local authorities that he deliver his grievances to a reporter in exchange for handing over the boy. Two people familiar with the early days of the operation corroborated The Daily Mails account, one adding that Dykes had a particular reporter in mind.
Dykes, who has lived in a travel trailer here for about two years, has a troubled past, including arrests on charges connected to drugs, drunken driving and, in Florida in 1995, unlawful display of a firearm. On Wednesday he was due in court in this county, accused of shooting at a neighbor in a dispute over driving on his property.
But the most telling indications of his troubles may lie outside the official record.
At midnight, when people would come home from late shifts, Dykes would be digging with a shovel in the red clay behind his trailer. Or he would be on patrol, walking the perimeter of his compound with a flashlight and a long gun.
Before building the bunker, Dykes made long, snaking mounds out of dirt and odd structures out of cinderblocks. He built the bunker in about three months, said a neighbor, Michael Creel, 28, who described it as 4 to 5 feet wide by 6 feet long, made of plywood and lined with plastic insulation and sandbags.
Creel said he was admiring Dykes okra bed one day when Dykes invited him to see the bunker.
It kind of threw me off the first time I climbed down in there, he said. He said, Climb down in there and holler, see if we can hear you. That was a little bit of a red flag.
Creel said he believed that Dykes had several handguns, including an antique Colt .45, as well as a rifle and a shotgun. Other neighbors said they had heard Dykes firing what sounded like a semiautomatic weapon in the field behind his property.
Creels father, Greg, said he had been subpoenaed to appear in the case involving the dispute with the neighbor. He said Dykes had given him a handwritten letter several pages long, presumably in connection with the trial.
Creel, 65, said he did not want to read the letter and had handed it over to law enforcement. I am sure it gives insight to this mans crazed mentality, he said.
Meanwhile, people in town continue to gather each night at a gazebo on the grounds of City Hall, where they hold candles in salt-filled plastic cups. Friday nights vigil began with announcements: a reminder to eat at the local Ruby Tuesday, which was making donations to the family.
A mother of one of the boys classmates spoke. There were prayers, for the family of the bus driver, Charles Albert Poland Jr., 66; for the boy and his family; even for Dykes.
They closed, as usual, with a chorus of Amazing Grace, and then resumed the long wait.MORE IN This Just InCity man faces Full StoryMan pleads guilty in beagles death Full StoryWAITSFIELD-A Vermont bank has been robbed twice in one week. Full Story -
- Most Popular
- Most Emailed
- RICHARD'S POOR ALMANACK: On this day 1739, 'Richard Palmer' identified in prison at York Castle as the notorious outlaw DICK TURPIN; IN 1836, Battle of the Alamo begins near San Antonio de Bexar, Texas; 1896, the Tootsie Roll invented by LEO HIRSCHFELD.
- RICHARD'S POOR ALMANACK: On this day in 1472, Orkney, Shetland islands put up as collateral by Norway to Scotland in lieu of dowry for MARGARET OF DENMARK on her marriage with JAMES III, king of Scotland; 1962, JOHN GLENN first American to orbit Earth.
- TOMORROW'S HEADLINES TODAY: City mayoral candidates debate campaign issues; Hartford, Conn., woman still missing; Neal Goswami reports attempts to legislate suicide; local woman loses 100 pounds through TOPS program.
- RICHARD'S POOR ALMANACK: On this day in 1878, JOHN TUNSTALL murdered near Lincoln, New Mexico, by the outlaw JESSE EVANS; in 1930, ELM FARM OLLIE first cow to fly in aircraft, first to be milked airborne; 1955, nuke test WASP; '79, snow in Sahara.
- TOMORROW'S HEADLINES TODAY: Rutland Herald News Editor Alan J. Keays and staff writer Gordon Dritschilo discuss stories planned for the February 18, 2015, edition of the newspaper: Winter budgets maxed, legal marijuana, Springfield bank job, USPS slowdown
- RICHARD'S POOR ALMANACK: On this day in 1249 AD, ANDRE of LONGJUMEAU is dispatched by LOUIS IX of France to meet the KHAGAN, ruler of the Mongol Empire; in 1804, during 1st Barbary War, STEPHEN DECATUR scuttles the pirate-held USS Philadelphia in Tripoli.

subset: commoncrawl


text:
Unlike vinyl furniture covers that deteriorate over time, this chaise lounge cover is made from woven polyester fabric that will never crack or peel. The pliant, 300-denier cover creates an impervious barrier to dirt, rain, snow, and sunlight. The edges are sewn, not heat-welded like lesser models, providing superior strength at the seams. The cover is UV-, heat-, and stain-resistant, and its PVC lining inhibits mold and mildew growth. Nylon cinch cords are strung through durable brass grommets, ensuring a tight fit. Stores in an included pouch when not in use. Hunter Green. Chaise Lounge Cover. 80" L x 30" W x 27" H. (4 1/2 lbs.)
Lifetime Guarantee
The Better Outdoor Furniture Covers (Chaise Lounge Cover) comes with The Hammacher Schlemmer Lifetime Guarantee at no additional charge. If this product ever disappoints you, for any reason, you may return your Hammacher Schlemmer purchase for exchange, credit, or refund.Should you have any questions, we are available 24 hours a day, seven days a week. Please call 1-800-321-1484 to speak with a product specialist or email us at email@example.com to receive a response within one hour.
May we recommend:
(based on 17 reviews)
Ratings Distribution
5 Stars
4 Stars
3 Stars
2 Stars
1 Stars
of respondents would recommend this to a friend.
Best Uses
Reviewed by 17 customers
Sort by
Displaying reviews 1-10
Back to top
Previous Page | Next Page »
(1 of 1 customers found this review helpful)
Fabric great, tie downs are cheap
By The Gardner
from Bradenton, FL
The product is constructed of a quality fabric. Size fits my outdoor set well. Tie downs are not of the same quality and will have to be re-constructed each time I take the cover off.
Share this Review
Our Third Set
By Mchael'sGirl
from St.Croix USVI
We've been buying these items over the past five years, as much as we like the green color for the outdoors sitting area, they do not hold up well in the sunshine of the US Virgin Islands. This time we are keeping our receipt and will send them back for exercise our "Lifetime Guarantee" and exchange.
Best ones yet.
By Garev
from Buckeye, AZ
I have chaise lounges both under my patio cover and on my lawn. I also purchased covers for my chairs last year. They fit perfectly (both the chair and chaise covers), look great, and are very well made. My only complaint is that they have already faded - after only one year.
Excellent Quality and Workmanship
By MMC
from Saskatoon Canada
Fits over our patio furniture very nicely. Easy to put on and take off. Will use a tote to store all the covers in when not in use n
Wonderful chaise lounge cover
By Sarah
from Lake Oswego
My new teak chaise lounge is longer than most, and this chaise lounge cover is long enough and deep enough to cover the entire chaise lounge plus a separate thick pad. I like the fact that the ties are not already fastened to the cover; it allows me to secure the cover to the slanted legs of the chaise lounge wherever I want.
The best looking covers
By Fred
from Allentown, PA
I am running out of room in my shed so the outdoor furniture covers will solve that problem
By PGS
from NW Wisconsin
Looking forward to see how the covers look after a long Wisconsin winter!
I am VERY pleased with my purchases!
By Todd
from Bethlehem, PA
We have two chaise lounges that have full length cushions that snap on to the lounge at the top (head) of the lounge. I was concerned that the cover would be a very tight fit - or not fit at all. much to my relief, the cover ( I only ordered one at first), fit perfectly. I then ordered the second, and am very pleased with them, even to my just lounging on the cover instead of taking it off. Thanks!
chaise lounge furniture cover
By beachgirl
from New York
I have an outdoor sectional and no covers are made for that size piece. The chaise cover worked well.
Perfect fit
By Pool lover
from Mesa, AZ
I purchased new chaise lounges this year and wanted to protect them from the hot Arizona sun. The covers fit perfectly and are really heavy duty.