Mailman Configuration Templates
Locate and customize mailman configuration templates using the current Jinja renderer and supported global override path.
The Mailman builder renders core mailing-list service settings for an installed Eenos Mailman service.
Locations and selection
| Type | Location |
|---|---|
| Shipped default | /usr/local/eenos/templates/mailman/mailman.cfg.jinja |
| Global custom override | /usr/local/eenos/templates/mailman/custom/mailman.cfg.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 destination is selected by the Mailman rebuild workflow. Core settings, web application configuration and webserver virtual hosts are separate parts of that deployment.
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 service identity, storage, mail transport and web integration consistent. A core config override does not replace all Mailman webserver templates or install Python requirements. Use the appropriate managed workflow and verify both list processing and the web interface.
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.