El 11 dic 2025 7:29 p. m., Chad Wallace via dovecot <[email protected]>
   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 <[email protected]> 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 -- [email protected]
     > To unsubscribe send an email to [email protected]

     --
     Chad Wallace
     Software Developer | The Lodging Company(R)
     P:  +1 250 869 4931 ext. 251
     TF: +1 888 676 9977
     E:  [email protected]
     W:  www.lodgingcompany.com
     _______________________________________________
     dovecot mailing list -- [email protected]
     To unsubscribe send an email to [email protected]

   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?
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to