Why doesn't Dovecot documentation specify which files to edit?
I've noticed that the official Dovecot documentation frequently omits crucial information about which specific files should be modified when configuring different functionalities. Concrete examples:
In the LMTP integration guide with Postfix (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-lm...):
It indicates to modify the socket configuration, but doesn't specify in which file this modification should be made
In the quota plugin documentation (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota):
It requests enabling the quota module, but doesn't mention the corresponding configuration file
I managed to achieve the configuration I wanted but it took more time than it should have. My question: I understand that Dovecot uses a modular configuration system and that technically I can place directives in any file. However, wouldn't it be clearer and more efficient if the documentation followed an established order and specified recommended locations? For example:
"Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf"
Is there a technical reason why the documentation deliberately avoids recommending specific files, or does it simply assume that users already know these conventions? Is there a general guide about Dovecot's configuration file structure and best practices for organizing them?
Thanks!
I think the configuration layout you're seeing may be provided by your distribution (Debian, RedHat, etc.). In the original release provided by Dovecot, I only see a single config file: dovecont.conf.in
Also, it is quite easy to find which file has certain types of configuration:
$ grep -ri lmtp /etc/dovecot
On Thu, 11 Dec 2025 20:47:44 +0000 n4ch0 via dovecot <dovecot@dovecot.org> wrote:
I've noticed that the official Dovecot documentation frequently omits crucial information about which specific files should be modified when configuring different functionalities. Concrete examples:
In the LMTP integration guide with Postfix (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-lm...):
It indicates to modify the socket configuration, but doesn't specify in which file this modification should be made
In the quota plugin documentation (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota):
It requests enabling the quota module, but doesn't mention the corresponding configuration file
I managed to achieve the configuration I wanted but it took more time than it should have. My question: I understand that Dovecot uses a modular configuration system and that technically I can place directives in any file. However, wouldn't it be clearer and more efficient if the documentation followed an established order and specified recommended locations? For example:
"Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf"
Is there a technical reason why the documentation deliberately avoids recommending specific files, or does it simply assume that users already know these conventions? Is there a general guide about Dovecot's configuration file structure and best practices for organizing them?
Thanks!
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
-- Chad Wallace Software Developer | The Lodging Company® P: +1 250 869 4931 ext. 251 TF: +1 888 676 9977 E: cwallace@lodgingcompany.com W: www.lodgingcompany.com
El 11 dic 2025 7:29 p. m., Chad Wallace via dovecot <dovecot@dovecot.org> escribio:
I think the configuration layout you're seeing may be provided by your
distribution (Debian, RedHat, etc.). In the original release provided
by Dovecot, I only see a single config file: dovecont.conf.in
Also, it is quite easy to find which file has certain types of
configuration:
$ grep -ri lmtp /etc/dovecot
On Thu, 11 Dec 2025 20:47:44 +0000
n4ch0 via dovecot <dovecot@dovecot.org> wrote:
> I've noticed that the official Dovecot documentation frequently omits
> crucial information about which specific files should be modified
> when configuring different functionalities. Concrete examples:
>
> In the LMTP integration guide with Postfix
>
(https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-lmtp):
>
> It indicates to modify the socket configuration, but doesn't specify
> in which file this modification should be made
>
>
> In the quota plugin documentation
>
(https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota):
>
> It requests enabling the quota module, but doesn't mention the
> corresponding configuration file
>
>
>
> I managed to achieve the configuration I wanted but it took more time
> than it should have. My question: I understand that Dovecot uses a
> modular configuration system and that technically I can place
> directives in any file. However, wouldn't it be clearer and more
> efficient if the documentation followed an established order and
> specified recommended locations? For example:
>
> "Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket"
> "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf"
>
> Is there a technical reason why the documentation deliberately avoids
> recommending specific files, or does it simply assume that users
> already know these conventions? Is there a general guide about
> Dovecot's configuration file structure and best practices for
> organizing them?
>
> Thanks!
> _______________________________________________
> dovecot mailing list -- dovecot@dovecot.org
> To unsubscribe send an email to dovecot-leave@dovecot.org
--
Chad Wallace
Software Developer | The Lodging Company(R)
P: +1 250 869 4931 ext. 251
TF: +1 888 676 9977
E: cwallace@lodgingcompany.com
W: www.lodgingcompany.com
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-leave@dovecot.orgOh, then it was my mistake to assume that Dovecot separated its configuration into multiple files and not that it originally does it in a single one. 100% my reading error. Thank you. What do you advise/recommend?
On Fri, Dec 12, 2025 at 07:12:28AM -0300, N4ch0 via dovecot wrote:
Oh, then it was my mistake to assume that Dovecot separated its configuration into multiple files and not that it originally does it in a single one. 100% my reading error. Thank you. What do you advise/recommend?
Distributions split files this way because it makes it easier for the distribution packages and the administrator to stay out of each other's way. It simplifies the process when upgrading packages, making it easier and more reliable for you to pick up new distro-provided configuration while preserving your modifications.
If you want to build up your own config from scratch and avoid whatever the distro provides, you may find it easier to use a single monolithic file. If you want to start from the distro configuration and only make changes as needed to suit the needs of your deployment, then stick with the split file layout.
noah (Debian dovecot maintainer)
12 de diciembre de 2025, 12:06, "Noah Meyerhans" <frodo@morgul.net mailto:frodo@morgul.net?to=%22Noah%20Meyerhans%22%20%3Cfrodo%40morgul.net%3E > escribió:
On Fri, Dec 12, 2025 at 07:12:28AM -0300, N4ch0 via dovecot wrote:
Oh, then it was my mistake to assume that Dovecot separated its configuration into multiple files and not that it originally does it in a single one. 100% my reading error. Thank you. What do you advise/recommend?
Distributions split files this way because it makes it easier for the distribution packages and the administrator to stay out of each other's way. It simplifies the process when upgrading packages, making it easier and more reliable for you to pick up new distro-provided configuration while preserving your modifications.
If you want to build up your own config from scratch and avoid whatever the distro provides, you may find it easier to use a single monolithic file. If you want to start from the distro configuration and only make changes as needed to suit the needs of your deployment, then stick with the split file layout.
noah (Debian dovecot maintainer)
Okay, that's clear. I've been using Debian for 15 years on both servers and desktops.
I used to use Courier on my mail servers, and now I've started using Dovecot. I didn't have any problems until I had to go to its official documentation and see how to configure the quota.
Everything's clear now, thanks for everything!
Hello all,
personally I like the split file layout, even on my small system, and use it where I can.
It makes it easy for 'testing' also, as you can 'remove' a whole file from the config. So if you change a bit of software (upgrade) / hardware and need new bits to make it work, it can be quick and easy to remove all the 'stuff' for that new bit if something has broken, and specify where error messages go for that specific part of the config (so you know that that new error message file is just available since the new config).
Also you can name a bit of config for a specific purpose, eg a database, and you know that the details within are specific to how that database interacts with other stuff.
I use this a lot as I have multiple different databases installed for testing stuff, and can then easily switch between if something doesn't work.
But I can also see that it can have dissagvantages, and you don't want to duplicate configs controls across different files, as it can become a mess to know which one has taken precendence !
D
Le ven. 12 déc. 2025 à 15:40, n4ch0 via dovecot <dovecot@dovecot.org> a écrit :
12 de diciembre de 2025, 12:06, "Noah Meyerhans" <frodo@morgul.net mailto: frodo@morgul.net?to=%22Noah%20Meyerhans%22%20%3Cfrodo%40morgul.net%3E > escribió:
On Fri, Dec 12, 2025 at 07:12:28AM -0300, N4ch0 via dovecot wrote:
Oh, then it was my mistake to assume that Dovecot separated its configuration into multiple files and not that it originally does it
in a
single one. 100% my reading error. Thank you. What do you advise/recommend?
Distributions split files this way because it makes it easier for the distribution packages and the administrator to stay out of each other's way. It simplifies the process when upgrading packages, making it easier and more reliable for you to pick up new distro-provided configuration while preserving your modifications.
If you want to build up your own config from scratch and avoid whatever the distro provides, you may find it easier to use a single monolithic file. If you want to start from the distro configuration and only make changes as needed to suit the needs of your deployment, then stick with the split file layout.
noah (Debian dovecot maintainer)
Okay, that's clear. I've been using Debian for 15 years on both servers and desktops.
I used to use Courier on my mail servers, and now I've started using Dovecot. I didn't have any problems until I had to go to its official documentation and see how to configure the quota.
Everything's clear now, thanks for everything!
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
Hello all, personally I like the split file layout, even on my small system, and use it where I can. It makes it easy for 'testing' also, as you can 'remove' a whole file from the config. So if you change a bit of software (upgrade) / hardware and need new bits to make it work, it can be quick and easy to remove all the 'stuff' for that new bit if something has broken, and specify where error messages go for that specific part of the config (so you know that that new error message file is just available since the new config). Also you can name a bit of config for a specific purpose, eg a database, and you know that the details within are specific to how that database interacts with other stuff. I use this a lot as I have multiple different databases installed for testing stuff, and can then easily switch between if something doesn't work. But I can also see that it can have dissagvantages, and you don't want to duplicate configs controls across different files, as it can become a mess to know which one has taken precendence ! D Le ven. 12 dec. 2025 `a 15:40, n4ch0 via dovecot <[1]dovecot@dovecot.org> a ecrit :
12 de diciembre de 2025, 12:06, "Noah Meyerhans" <[2]frodo@morgul.net
mailto:[3]frodo@morgul.net?to=%22Noah%20Meyerhans%22%20%3Cfrodo%[4]40morgul.net%3E
> escribio:
>
> On Fri, Dec 12, 2025 at 07:12:28AM -0300, N4ch0 via dovecot wrote:
>
> >
> > Oh, then it was my mistake to assume that Dovecot separated its
> > configuration into multiple files and not that it originally does
it in a
> > single one.
> > 100% my reading error. Thank you.
> > What do you advise/recommend?
> >
> Distributions split files this way because it makes it easier for the
> distribution packages and the administrator to stay out of each
other's
> way. It simplifies the process when upgrading packages, making it
> easier and more reliable for you to pick up new distro-provided
> configuration while preserving your modifications.
>
> If you want to build up your own config from scratch and avoid
whatever
> the distro provides, you may find it easier to use a single monolithic
> file. If you want to start from the distro configuration and only make
> changes as needed to suit the needs of your deployment, then stick
with
> the split file layout.
>
> noah
> (Debian dovecot maintainer)
>
Okay, that's clear. I've been using Debian for 15 years on both servers
and desktops.
I used to use Courier on my mail servers, and now I've started using
Dovecot. I didn't have any problems until I had to go to its official
documentation and see how to configure the quota.
Everything's clear now, thanks for everything!
_______________________________________________
dovecot mailing list -- [5]dovecot@dovecot.org
To unsubscribe send an email to [6]dovecot-leave@dovecot.orgReferences
Visible links
- mailto:dovecot@dovecot.org
- mailto:frodo@morgul.net
- mailto:frodo@morgul.net
- http://40morgul.net/
- mailto:dovecot@dovecot.org
- mailto:dovecot-leave@dovecot.org
On Sat Dec 13, 2025 at 4:10 PM -03, David Myers via dovecot wrote:
Hello all,
personally I like the split file layout, even on my small system, and use it where I can.
It makes it easy for 'testing' also, as you can 'remove' a whole file from the config. So if you change a bit of software (upgrade) / hardware and need new bits to make it work, it can be quick and easy to remove all the 'stuff' for that new bit if something has broken, and specify where error messages go for that specific part of the config (so you know that that new error message file is just available since the new config).
Also you can name a bit of config for a specific purpose, eg a database, and you know that the details within are specific to how that database interacts with other stuff.
I use this a lot as I have multiple different databases installed for testing stuff, and can then easily switch between if something doesn't work.
But I can also see that it can have dissagvantages, and you don't want to duplicate configs controls across different files, as it can become a mess to know which one has taken precendence !
D
Le ven. 12 déc. 2025 à 15:40, n4ch0 via dovecot <dovecot@dovecot.org> a écrit :
12 de diciembre de 2025, 12:06, "Noah Meyerhans" <frodo@morgul.net mailto: frodo@morgul.net?to=%22Noah%20Meyerhans%22%20%3Cfrodo%40morgul.net%3E > escribió:
On Fri, Dec 12, 2025 at 07:12:28AM -0300, N4ch0 via dovecot wrote:
Oh, then it was my mistake to assume that Dovecot separated its configuration into multiple files and not that it originally does it
in a
single one. 100% my reading error. Thank you. What do you advise/recommend?
Distributions split files this way because it makes it easier for the distribution packages and the administrator to stay out of each other's way. It simplifies the process when upgrading packages, making it easier and more reliable for you to pick up new distro-provided configuration while preserving your modifications.
If you want to build up your own config from scratch and avoid whatever the distro provides, you may find it easier to use a single monolithic file. If you want to start from the distro configuration and only make changes as needed to suit the needs of your deployment, then stick with the split file layout.
noah (Debian dovecot maintainer)
Okay, that's clear. I've been using Debian for 15 years on both servers and desktops.
I used to use Courier on my mail servers, and now I've started using Dovecot. I didn't have any problems until I had to go to its official documentation and see how to configure the quota.
Everything's clear now, thanks for everything!
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
That’s exactly what I ran into when I started configuring quotas in Dovecot: I ended up with duplicated controls. It was also my fault, because the documentation floating around on the internet refers to the syntax of older Dovecot versions, and when I finally got to the official documentation I ran into what started this thread.
participants (5)
-
Chad Wallace
-
David Myers
-
n4ch0
-
N4ch0
-
Noah Meyerhans