Dovecot Versioned Templates
Customize Dovecot settings using version-specific Jinja defaults and custom overrides for the detected server version.
The Dovecot rebuild detects the installed version and selects the matching template family, such as 2.3 or 2.4. These configurations are not interchangeable.
Versioned locations
| Type | Location |
|---|---|
| Shipped templates | /usr/local/eenos/templates/dovecot/<version>/ |
| Global custom overrides | /usr/local/eenos/templates/dovecot/<version>/custom/ |
For each selected filename, a matching custom file overrides its same-version default. The old unversioned dovecot/custom/ location is not the current rebuild's lookup path.
The template set includes dovecot.conf.jinja, dovecot-auth.conf.jinja, dovecot-master.conf.jinja, dovecot-mail.conf.jinja and dovecot-ssl.conf.jinja, plus protocol-specific IMAP, POP3, LMTP and ManageSieve files where applicable. The caller maps these to /etc/dovecot/dovecot.conf and the corresponding conf.d files. Missing required templates cause a rebuild error.
Review the correct version
Clone a compatible file into the versioned custom directory and preserve authentication, mail storage, TLS, service sockets and protocol behavior. A 2.3 directive or variable cannot be assumed valid in 2.4. Review changes to both the shipped template and its supplied data after an upgrade.
Validate the generated configuration with installed Dovecot tooling before activation. Check authentication and representative mailbox/protocol access on a test system. Preserve a working template/configuration pair for rollback; a template edit does not automatically change every running process.
Use WAP Dovecot for operational settings. These templates have global service scope, not a per-mailbox override contract.