37
Prebuilt packages usually install the configuration files into '/etc/dovecot/'.
38
You'll find the correct path by running:
40
---%<-------------------------------------------------------------------------
41
doveconf -n | head -n 1
42
---%<-------------------------------------------------------------------------
44
It's a good idea to read through all the config files and see what settings you
47
Installing from sources
48
-----------------------
33
50
If you compiled and installed Dovecot from sources, Dovecot has installed only
34
51
a '/usr/local/etc/dovecot/README' file, which contains the path to the
35
52
installed example configuration files, usually
36
'/usr/local/share/doc/dovecot/example-config'. Copy the 'dovecot.conf' file and
37
'conf.d' directory from the example-config directory into
38
'/usr/local/etc/dovecot/'. Prebuilt packages usually install the configuration
39
files directly into '/etc/dovecot/'.
40
You'll find the path by running 'doveconf -n | head -n 1'.
41
It's a good idea to read through all the files and see what settings you might
53
'/usr/local/share/doc/dovecot/example-config'. Copy them to etc/:
55
---%<-------------------------------------------------------------------------
56
cp -r /usr/local/share/doc/dovecot/example-config/* /usr/local/etc/dovecot/
57
---%<-------------------------------------------------------------------------
59
Split configuration files
60
-------------------------
44
62
The default configuration starts from 'dovecot.conf', which contains an
45
'!include conf.d/*.conf' statement to read the rest of the configuration. This
46
split of configuration files isn't a requirement to use, and it doesn't really
47
matter which .conf file you add any particular setting, just as long as it
48
isn't overridden in another file. You can verify with 'doveconf -n' that
49
everything looks as you intended.
63
'!include conf.d/*.conf' statement to read the rest of the configuration. The
64
idea is that the settings are nicely grouped into different files to make it
65
easier for new admins to scan through related settings. It doesn't matter which
66
config file you add which setting. In the production system it's often easier
67
to just have a single 'dovecot.conf' file, which you can create easily using
69
---%<-------------------------------------------------------------------------
70
doveconf -n > dovecot.conf
71
---%<-------------------------------------------------------------------------
104
126
'ssl = no'. Easiest way to get SSL certificates built is to use Dovecot's
105
127
'doc/mkcert.sh' script. See <SSL.txt>.
107
By default Dovecot doesn't allow users to send passwords unencrypted to the
108
server. Usually if SSL is enabled, it's a good idea not to allow this. However,
109
if you don't offer SSL for some reason, you'll probably want to set
110
'disable_plaintext_auth = no'.
129
By default 'disable_plaintext_auth = yes', which means that Dovecot will fail
130
the authentication if the client doesn't use SSL (or use <non-plaintext
131
authentication> [Authentication.Mechanisms.txt]). This is recommended in most
132
situations, since it prevents leaking passwords. However, if you don't offer
133
SSL for some reason, you'll probably want to set 'disable_plaintext_auth = no'.