Skip to Content
Browse documentation

Exim Configuration Templates

Locate and customize exim configuration templates using the current Jinja renderer and supported global override path.

Exim templates generate the SMTP server configuration. The associated Perl startup helper has its own override selection.

Locations and selection

TypeLocation
Shipped default/usr/local/eenos/templates/exim/exim.conf.jinja
Global custom override/usr/local/eenos/templates/exim/custom/exim.conf.jinja

The reviewed caller checks the matching custom file before its default. It does not implement an account-specific override for this component. Use the Jinja syntax and data expected by that caller, regardless of the filename extension.

The reviewed builder writes /etc/exim/exim.conf and selects /etc/exim/exim.pl from the default or custom exim.pl source.

Customize and validate

Copy the current compatible default into the supported custom location, edit the copy and retain the prior version. Do not modify the shipped template or only edit an automatically generated destination file: a later rebuild can replace it.

Keep Exim configuration and Perl helpers compatible. Current feature activation can depend on helper subroutines, including mail-limit accounting and domain relay selection. Reusing an old custom helper can omit current capabilities even if the main configuration renders. Preserve routing, authentication, filtering and accounting controls; validate with the installed Exim tooling before a planned activation.

Review the rendered output in staging and the component's native validation result. Template rendering alone does not prove usable service configuration. Apply a planned rebuild/reload only after review, and keep a working template/output pair for rollback.

After updates, compare your override with the new shipped default and merge required changes. See the panel administration guide and template rollout guidance.