This commit is contained in:
github-actions[bot] committed 2026-11-18 16:59:56 +00:00
1 parent 7202446ae2
commit 07ffcc59c1
7 files changed
+39 -18

No files matched your search

+1 -1
View File
@@ -3055,7 +3055,7 @@
<ul>
<li>If you omit the <code>INBOX.</code> prefix from the sieve script above, the mailbox (folder) for that tag is created at the top-level alongside your Trash and Junk folders.</li>
<li>The <code>.</code> between <code>INBOX</code> and <code>${tag}</code> is important as a <a href="https://doc.dovecot.org/configuration_manual/sieve/usage/#mailbox-names">separator to distinguish mailbox names</a>. This can vary by mailbox format or configuration. DMS uses <a href="https://doc.dovecot.org/admin_manual/mailbox_formats/maildir/#maildir-mbox-format"><code>Maildir</code></a> by default, which uses <code>.</code> as the separator.</li>
<li><a href="https://doc.dovecot.org/settings/core/#core_setting-lmtp_save_to_detail_mailbox"><code>lmtp_save_to_detail_mailbox = yes</code></a> can be set in <code>/etc/dovecot/conf.d/20-lmtp.conf</code>:<ul>
<li><a href="https://doc.dovecot.org/settings/core/#core_setting-lmtp_save_to_detail_mailbox"><code>lmtp_save_to_detail_mailbox = yes</code></a> can be set in your <a href="../override-defaults/dovecot/#add-configuration"><code>dovecot.cf</code></a>:<ul>
<li>This implements the feature globally, except for the tag normalization and <code>INBOX.</code> prefix parts of the example script.</li>
<li>However, if the sieve script is also present, the script has precedence and will handle this task instead when the condition is successful, otherwise falling back to the global feature.</li>
</ul>
@@ -2963,7 +2963,7 @@
<h1>Dovecot</h1>
<h2 id="add-configuration"><a class="toclink" href="#add-configuration">Add Configuration</a></h2>
<p>The Dovecot default configuration can easily be extended providing a <code>docker-data/dms/config/dovecot.cf</code> file.
<p>The Dovecot configuration of DMS can easily be extended providing a <code>docker-data/dms/config/dovecot.cf</code> file.
<a href="https://doc.dovecot.org/configuration_manual/">Dovecot documentation</a> remains the best place to find configuration options.</p>
<p>Your DMS folder structure should look like this example:</p>
<div class="highlight"><pre><span></span><code>├── docker-data/dms/config
@@ -2979,16 +2979,27 @@
<p>Another important option is the <code>default_process_limit</code> (defaults to <code>100</code>). If high-security mode is enabled you'll need to make sure this count is higher than the maximum number of users that can be logged in simultaneously.</p>
<p>This limit is quickly reached if users connect to DMS with multiple end devices.</p>
<h2 id="override-configuration"><a class="toclink" href="#override-configuration">Override Configuration</a></h2>
<p>For major configuration changes it’s best to override the dovecot configuration files. For each configuration file you want to override, add a list entry under the <code>volumes</code> key.</p>
<p>DMS ships its own, self-contained Dovecot configuration. It does not depend on the configuration files that Debian or the Dovecot Community Edition (CE) packages provide. The main file <code>/etc/dovecot/dovecot.conf</code> is read by Dovecot in this order:</p>
<ol>
<li>The settings of DMS itself (<em><code>/etc/dovecot/dovecot.conf</code>, some of them are adjusted at startup according to ENV</em>)</li>
<li>All <code>*.conf</code> files in <code>/etc/dovecot/features.d/</code> (<em>features that DMS enabled</em>)</li>
<li>All <code>*.conf</code> files in <code>/etc/dovecot/conf.d/</code> (<em>your own files</em>)</li>
<li><code>/etc/dovecot/local.conf</code> (<em>your <code>dovecot.cf</code></em>)</li>
</ol>
<p>Settings that are read later override earlier ones, while sections like <code>namespace</code> or <code>mailbox</code> and boolean lists like <code>mail_plugins</code> are merged. Thus you rarely need to replace a file: add your own file to <code>/etc/dovecot/conf.d/</code> instead. It overrides the features, regardless of its file name. For each file you want to add, add a list entry under the <code>volumes</code> key:</p>
<div class="highlight"><pre><span></span><code><span class="nt">services</span><span class="p">:</span>
<span class="w"> </span><span class="nt">mailserver</span><span class="p">:</span>
<span class="w"> </span><span class="nt">volumes</span><span class="p">:</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/mail-data/:/var/mail/</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/10-master.conf:/etc/dovecot/conf.d/10-master.conf</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/90-custom.conf:/etc/dovecot/conf.d/90-custom.conf:ro</span>
</code></pre></div>
<p>You will first need to obtain the configuration from the running container (<em>where <code>mailserver</code> is the container name</em>):</p>
<div class="highlight"><pre><span></span><code>mkdir<span class="w"> </span>-p<span class="w"> </span>./docker-data/dms/config/dovecot
docker<span class="w"> </span>cp<span class="w"> </span>mailserver:/etc/dovecot/conf.d/10-master.conf<span class="w"> </span>./docker-data/dms/config/dovecot/10-master.conf
<div class="admonition note">
<p class="admonition-title">Features</p>
<p>DMS copies the optional features it enables from <code>/etc/dovecot/features/</code> to <code>/etc/dovecot/features.d/</code> during startup (<em><code>auth-passwdfile.conf</code>, <code>auth-ldap.conf</code>, <code>auth-oauth2.conf</code>, <code>quota.conf</code> and <code>rspamd-learn.conf</code></em>). Any file in <code>conf.d/</code> overrides them.</p>
<p>To adjust a feature, override its settings in your own file or in <code>dovecot.cf</code>. To inspect it, run <code>docker exec mailserver cat /etc/dovecot/features/&lt;NAME&gt;.conf</code>.</p>
</div>
<p>You can obtain the configuration of DMS from the running container (<em>where <code>mailserver</code> is the container name</em>), to see which settings you can override:</p>
<div class="highlight"><pre><span></span><code>docker<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>mailserver<span class="w"> </span>cat<span class="w"> </span>/etc/dovecot/dovecot.conf
</code></pre></div>
<h2 id="statistics"><a class="toclink" href="#statistics">Statistics</a></h2>
<p>DMS keeps Dovecot's upstream defaults for the <code>stats</code> service. To verify it works, run:</p>
+1 -1
View File
@@ -7003,7 +7003,7 @@ Spaces are not trimmed, so <code>user1, user2</code> does not select <code>user2
<li>yes =&gt; LDAP over TLS enabled for Dovecot</li>
</ul>
<h4 id="dovecot"><a class="toclink" href="#dovecot">Dovecot</a></h4>
<p>The following variables overwrite the default values for <code>/etc/dovecot/conf.d/auth-ldap.conf.ext</code>.</p>
<p>The following variables overwrite the default values for <code>/etc/dovecot/features.d/auth-ldap.conf</code>.</p>
<h5 id="dovecot_base"><a class="toclink" href="#dovecot_base">DOVECOT_BASE</a></h5>
<ul>
<li><strong>empty</strong> =&gt; same as <code>LDAP_SEARCH_BASE</code></li>
+6 -3
View File
@@ -3019,8 +3019,6 @@
<summary>Add to DMS volumes in <code>compose.yaml</code></summary>
<div class="highlight"><pre><span></span><code><span class="w"> </span><span class="c1"># All new volumes are marked :ro to configure them as read-only, since their contents are not changed from inside the container</span>
<span class="w"> </span><span class="nt">volumes</span><span class="p">:</span>
<span class="w"> </span><span class="c1"># Configuration override to disable LDAP authentication</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/auth-ldap.conf.ext:/etc/dovecot/conf.d/auth-ldap.conf.ext:ro</span>
<span class="w"> </span><span class="c1"># Configuration addition to enable Lua authentication</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/auth-lua-httpbasic.conf:/etc/dovecot/conf.d/auth-lua-httpbasic.conf:ro</span>
<span class="w"> </span><span class="c1"># Directory containing Lua scripts</span>
@@ -3030,12 +3028,17 @@
<p>Create a directory for Lua scripts:
<div class="highlight"><pre><span></span><code>mkdir<span class="w"> </span>-p<span class="w"> </span>./docker-data/dms/config/dovecot/lua
</code></pre></div></p>
<p>Create configuration file <code>./docker-data/dms/config/dovecot/auth-ldap.conf.ext</code> for LDAP user provisioning:
<p>Create configuration file <code>./docker-data/dms/config/dovecot/auth-ldap.conf</code> for LDAP user provisioning:
<div class="highlight"><pre><span></span><code>userdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
</code></pre></div></p>
<p>DMS creates <code>/etc/dovecot/features.d/auth-ldap.conf</code> during startup (including LDAP authentication) when using LDAP for account provisioning. To replace it with the configuration above, which only provisions users, add a <code>user-patches.sh</code> to <code>./docker-data/dms/config/</code>:
<div class="highlight"><pre><span></span><code><span class="ch">#!/bin/bash</span>
cp<span class="w"> </span>/tmp/docker-mailserver/dovecot/auth-ldap.conf<span class="w"> </span>/etc/dovecot/features.d/auth-ldap.conf
</code></pre></div></p>
<p>Create configuration file <code>./docker-data/dms/config/dovecot/auth-lua-httpbasic.conf</code> for Lua user authentication:
<div class="highlight"><pre><span></span><code>passdb {
driver = lua
@@ -3031,14 +3031,21 @@
<h1 id="mailboxes-aka-imap-folders"><a class="toclink" href="#mailboxes-aka-imap-folders">Mailboxes (<em>aka IMAP Folders</em>)</a></h1>
<p><code>INBOX</code> is setup as the private <a href="https://doc.dovecot.org/configuration_manual/namespace/#namespace-inbox"><code>inbox</code> namespace</a>. By default <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/15-mailboxes.conf"><code>target/dovecot/15-mailboxes.conf</code></a> configures the special IMAP folders <code>Drafts</code>, <code>Sent</code>, <code>Junk</code> and <code>Trash</code> to be automatically created and subscribed. They are all assigned to the private <a href="https://doc.dovecot.org/configuration_manual/namespace/#namespace-inbox"><code>inbox</code> namespace</a> (<em>which implicitly provides the <code>INBOX</code> folder</em>).</p>
<p><code>INBOX</code> is setup as the private <a href="https://doc.dovecot.org/configuration_manual/namespace/#namespace-inbox"><code>inbox</code> namespace</a>. By default the <code>namespace inbox</code> section of <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/dovecot.conf"><code>target/dovecot/dovecot.conf</code></a> configures the special IMAP folders <code>Drafts</code>, <code>Sent</code>, <code>Junk</code> and <code>Trash</code> to be automatically created and subscribed. They are all assigned to the private <a href="https://doc.dovecot.org/configuration_manual/namespace/#namespace-inbox"><code>inbox</code> namespace</a> (<em>which implicitly provides the <code>INBOX</code> folder</em>).</p>
<p>These IMAP folders are considered special because they add a <a href="https://datatracker.ietf.org/doc/html/rfc6154"><em>"SPECIAL-USE"</em> attribute</a>, which is a standardized way to communicate to mail clients that the folder serves a purpose like storing spam/junk mail (<code>\Junk</code>) or deleted mail (<code>\Trash</code>). This differentiates them from regular mail folders that you may use for organizing.</p>
<h2 id="adding-a-mailbox-folder"><a class="toclink" href="#adding-a-mailbox-folder">Adding a mailbox folder</a></h2>
<p>See <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/15-mailboxes.conf"><code>target/dovecot/15-mailboxes.conf</code></a> for existing mailbox folders which you can modify or uncomment to enable some other common mailboxes. For more information try the <a href="https://doc.dovecot.org/configuration_manual/namespace/#mailbox-settings">official Dovecot documentation</a>.</p>
<p>The <code>Archive</code> special IMAP folder may be useful to enable. To do so, make a copy of <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/15-mailboxes.conf"><code>target/dovecot/15-mailboxes.conf</code></a> and uncomment the <code>Archive</code> mailbox definition. Mail clients should understand that this folder is intended for archiving mail due to the <a href="https://datatracker.ietf.org/doc/html/rfc6154"><code>\Archive</code> <em>"SPECIAL-USE"</em> attribute</a>.</p>
<p>With the provided <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/compose.yaml">compose.yaml</a> example, a volume bind mounts the host directory <code>docker-data/dms/config/</code> to the container location <code>/tmp/docker-mailserver/</code>. Config file overrides should instead be mounted to a different location as described in <a href="../../../config/advanced/override-defaults/dovecot/#override-configuration">Overriding Configuration for Dovecot</a>:</p>
<p>See the <code>namespace inbox</code> section of <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/target/dovecot/dovecot.conf"><code>target/dovecot/dovecot.conf</code></a> for the existing mailbox folders. For more information try the <a href="https://doc.dovecot.org/configuration_manual/namespace/#mailbox-settings">official Dovecot documentation</a>.</p>
<p>The <code>Archive</code> special IMAP folder may be useful to enable. To do so, add the <code>Archive</code> mailbox definition in a Dovecot config file of your own. Mail clients should understand that this folder is intended for archiving mail due to the <a href="https://datatracker.ietf.org/doc/html/rfc6154"><code>\Archive</code> <em>"SPECIAL-USE"</em> attribute</a>.</p>
<div class="highlight"><span class="filename">docker-data/dms/config/dovecot/90-mailboxes.conf</span><pre><span></span><code><span class="na">namespace inbox {</span>
<span class="w"> </span><span class="na">mailbox Archive {</span>
<span class="w"> </span><span class="na">auto</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">subscribe</span>
<span class="w"> </span><span class="na">special_use</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s">\Archive</span>
<span class="w"> </span><span class="na">}</span>
<span class="na">}</span>
</code></pre></div>
<p>With the provided <a href="https://github.com/docker-mailserver/docker-mailserver/blob/master/compose.yaml">compose.yaml</a> example, a volume bind mounts the host directory <code>docker-data/dms/config/</code> to the container location <code>/tmp/docker-mailserver/</code>. Your Dovecot config file should instead be mounted to a different location as described in <a href="../../../config/advanced/override-defaults/dovecot/#override-configuration">Overriding Configuration for Dovecot</a>. Alternatively, add the same content to <a href="../../../config/advanced/override-defaults/dovecot/#override-configuration"><code>dovecot.cf</code></a>.</p>
<div class="highlight"><pre><span></span><code><span class="nt">volumes</span><span class="p">:</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/15-mailboxes.conf:/etc/dovecot/conf.d/15-mailboxes.conf:ro</span>
<span class="w"> </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">./docker-data/dms/config/dovecot/90-mailboxes.conf:/etc/dovecot/conf.d/90-mailboxes.conf:ro</span>
</code></pre></div>
<h2 id="caution"><a class="toclink" href="#caution">Caution</a></h2>
<h3 id="adding-folders-to-an-existing-setup"><a class="toclink" href="#adding-folders-to-an-existing-setup">Adding folders to an existing setup</a></h3>
@@ -3232,7 +3232,7 @@ docker<span class="w"> </span>compose<span class="w"> </span>up<span class="w">
<h2 id="other-configuration-options"><a class="toclink" href="#other-configuration-options">Other configuration options</a></h2>
<p>Both device registration and notifications send a username to the daemon to lookup the device. While the registration and other IMAP operations in Dovecot will send the Dovecot username, LMTP will send the provided authentication username.</p>
<p>The format of that username is specified by the <code>auth_username_format</code> Dovecot setting. If you are not using mail addresses as Dovecot usernames - e.g. when using LDAP - you can either change the <code>auth_username_format</code> or add the mail address as property to the user account and use the lookup feature (see below).</p>
<div class="highlight"><span class="filename">user-patches.sh</span><pre><span></span><code>sed<span class="w"> </span>-i<span class="w"> </span>-r<span class="w"> </span><span class="s2">&quot;s|^#?(auth_username_format =).*|\1 %Ln|&quot;</span><span class="w"> </span>/etc/dovecot/conf.d/10-auth.conf
<div class="highlight"><span class="filename">user-patches.sh</span><pre><span></span><code><span class="nb">echo</span><span class="w"> </span><span class="s1">&#39;auth_username_format = %{user | username | lower}&#39;</span><span class="w"> </span>&gt;/etc/dovecot/conf.d/90-xaps-username.conf
</code></pre></div>
<p>You can also use notifications for Dovecot alias mailboxes. Depending on your server configuration, this might require to add the original Dovecot username as <a href="https://doc.dovecot.org/configuration_manual/authentication/user_database_extra_fields/">Dovecot attribute</a> to the login user as well as changing the <code>user_lookup=theattribute</code> in <code>95-xaps.conf</code> to perform the lookup of that attribute.</p>
+1 -1
View File
@@ -1 +1 @@
{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"","title":"Welcome to the Documentation for <code>docker-mailserver</code>!","text":"<p>This Documentation is Versioned</p> <p>Make sure to select the correct version of this documentation! It should match the version of the image you are using. The default version corresponds to the <code>:latest</code> image tag - the most recent stable release.</p> <p>This documentation provides you not only with the basic setup and configuration of DMS but also with advanced configuration, elaborate usage scenarios, detailed examples, hints and more.</p>"},{"location":"#about","title":"About","text":"<p><code>docker-mailserver</code>, or DMS for short, is a production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Anti-spam, Anti-virus, etc.). It employs only configuration files, no SQL database. The image is focused around the slogan \"Keep it simple and versioned\".</p>"},{"location":"#contents","title":"Contents","text":""},{"location":"#getting-started","title":"Getting Started","text":"<p>If you're completely new to mail servers or you want to read up on them, check out our Introduction page. If you're new to DMS as a mail server appliance, make sure to read the Usage chapter first. If you want to look at examples for Docker Compose, we have an Examples page.</p> <p>There is also a script - <code>setup.sh</code> - supplied with this project. It supports you in configuring and administrating your server. Information on how to get it and how to use it is available on a dedicated page.</p>"},{"location":"#configuration","title":"Configuration","text":"<p>We have a dedicated configuration page. It contains most of the configuration and explanation you need to setup your mail server properly. Be aware that advanced tasks may still require reading through all parts of this documentation; it may also involve inspecting your running container for debugging purposes. After all, a mail server is a complex arrangement of various programs.</p> <p>Important</p> <p>If you'd like to change, patch or alter files or behavior of DMS, you can use a script. Just place a script called <code>user-patches.sh</code> in your <code>./docker-data/dms/config/</code> folder volume (which is mounted to <code>/tmp/docker-mailserver/</code> inside the container) and it will be run on container startup. See the 'Modifications via Script' page for additional documentation and an example.</p> <p>You might also want to check out:</p> <ol> <li>A list of all configuration options via ENV</li> <li>A list of all optional and automatically created configuration files and directories</li> <li>How to debug your mail server</li> </ol> <p>Tip</p> <p>Definitely check out the FAQ for more information and tips! Please do not open an issue before you have checked our documentation for answers, including the FAQ!</p>"},{"location":"#tests","title":"Tests","text":"<p>DMS employs a variety of tests. If you want to know more about our test suite, view our testing docs.</p>"},{"location":"#contributing","title":"Contributing","text":"<p>We are always happy to welcome new contributors. For guidelines and entrypoints please have a look at the Contributing section.</p>"},{"location":"faq/","title":"FAQ","text":""},{"location":"faq/#what-kind-of-database-are-you-using","title":"What kind of database are you using?","text":"<p>None! No database is required. The filesystem is the database. This image is based on config files that can be persisted using bind mounts (default) or Docker volumes, and as such versioned, backed up and so forth.</p>"},{"location":"faq/#where-are-emails-stored","title":"Where are emails stored?","text":"<p>Mails are stored in <code>/var/mail/${domain}/${username}</code>. Since <code>v9.0.0</code> it is possible to add custom <code>user_attributes</code> for each accounts to have a different mailbox configuration (See #1792).</p>"},{"location":"faq/#how-are-imap-mailboxes-aka-imap-folders-set-up","title":"How are IMAP mailboxes (aka IMAP Folders) set up?","text":"<p><code>INBOX</code> is setup by default with the special IMAP folders <code>Drafts</code>, <code>Sent</code>, <code>Junk</code> and <code>Trash</code>. You can learn how to modify or add your own folders (including additional special folders like <code>Archive</code>) by visiting our docs page Customizing IMAP Folders for more information.</p>"},{"location":"faq/#how-do-i-update-dms","title":"How do I update DMS?","text":"<p>Make sure to read the CHANGELOG before updating to new versions, to be prepared for possible breaking changes.</p> <p>Then, run the following commands:</p> <pre><code>docker compose pull\ndocker compose down\ndocker compose up -d\n</code></pre> <p>You should see the new version number on startup, for example: <code>[ INF ] Welcome to docker-mailserver 11.3.1</code>. AndLine truncated
{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"","title":"Welcome to the Documentation for <code>docker-mailserver</code>!","text":"<p>This Documentation is Versioned</p> <p>Make sure to select the correct version of this documentation! It should match the version of the image you are using. The default version corresponds to the <code>:latest</code> image tag - the most recent stable release.</p> <p>This documentation provides you not only with the basic setup and configuration of DMS but also with advanced configuration, elaborate usage scenarios, detailed examples, hints and more.</p>"},{"location":"#about","title":"About","text":"<p><code>docker-mailserver</code>, or DMS for short, is a production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Anti-spam, Anti-virus, etc.). It employs only configuration files, no SQL database. The image is focused around the slogan \"Keep it simple and versioned\".</p>"},{"location":"#contents","title":"Contents","text":""},{"location":"#getting-started","title":"Getting Started","text":"<p>If you're completely new to mail servers or you want to read up on them, check out our Introduction page. If you're new to DMS as a mail server appliance, make sure to read the Usage chapter first. If you want to look at examples for Docker Compose, we have an Examples page.</p> <p>There is also a script - <code>setup.sh</code> - supplied with this project. It supports you in configuring and administrating your server. Information on how to get it and how to use it is available on a dedicated page.</p>"},{"location":"#configuration","title":"Configuration","text":"<p>We have a dedicated configuration page. It contains most of the configuration and explanation you need to setup your mail server properly. Be aware that advanced tasks may still require reading through all parts of this documentation; it may also involve inspecting your running container for debugging purposes. After all, a mail server is a complex arrangement of various programs.</p> <p>Important</p> <p>If you'd like to change, patch or alter files or behavior of DMS, you can use a script. Just place a script called <code>user-patches.sh</code> in your <code>./docker-data/dms/config/</code> folder volume (which is mounted to <code>/tmp/docker-mailserver/</code> inside the container) and it will be run on container startup. See the 'Modifications via Script' page for additional documentation and an example.</p> <p>You might also want to check out:</p> <ol> <li>A list of all configuration options via ENV</li> <li>A list of all optional and automatically created configuration files and directories</li> <li>How to debug your mail server</li> </ol> <p>Tip</p> <p>Definitely check out the FAQ for more information and tips! Please do not open an issue before you have checked our documentation for answers, including the FAQ!</p>"},{"location":"#tests","title":"Tests","text":"<p>DMS employs a variety of tests. If you want to know more about our test suite, view our testing docs.</p>"},{"location":"#contributing","title":"Contributing","text":"<p>We are always happy to welcome new contributors. For guidelines and entrypoints please have a look at the Contributing section.</p>"},{"location":"faq/","title":"FAQ","text":""},{"location":"faq/#what-kind-of-database-are-you-using","title":"What kind of database are you using?","text":"<p>None! No database is required. The filesystem is the database. This image is based on config files that can be persisted using bind mounts (default) or Docker volumes, and as such versioned, backed up and so forth.</p>"},{"location":"faq/#where-are-emails-stored","title":"Where are emails stored?","text":"<p>Mails are stored in <code>/var/mail/${domain}/${username}</code>. Since <code>v9.0.0</code> it is possible to add custom <code>user_attributes</code> for each accounts to have a different mailbox configuration (See #1792).</p>"},{"location":"faq/#how-are-imap-mailboxes-aka-imap-folders-set-up","title":"How are IMAP mailboxes (aka IMAP Folders) set up?","text":"<p><code>INBOX</code> is setup by default with the special IMAP folders <code>Drafts</code>, <code>Sent</code>, <code>Junk</code> and <code>Trash</code>. You can learn how to modify or add your own folders (including additional special folders like <code>Archive</code>) by visiting our docs page Customizing IMAP Folders for more information.</p>"},{"location":"faq/#how-do-i-update-dms","title":"How do I update DMS?","text":"<p>Make sure to read the CHANGELOG before updating to new versions, to be prepared for possible breaking changes.</p> <p>Then, run the following commands:</p> <pre><code>docker compose pull\ndocker compose down\ndocker compose up -d\n</code></pre> <p>You should see the new version number on startup, for example: <code>[ INF ] Welcome to docker-mailserver 11.3.1</code>. AndLine truncated