SpamAssassin Configuration Templates
Locate and customize spamassassin configuration templates using the current Jinja renderer and supported global override path.
The spam-filter builder renders spamd policy from its current configuration when the service is installed.
Locations and selection
| Type | Location |
|---|---|
| Shipped default | /usr/local/eenos/templates/spamassassin/local.cf.jinja |
| Global custom override | /usr/local/eenos/templates/spamassassin/custom/local.cf.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/spamassassin/local.cf.
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.
Preserve valid rule syntax, score settings and service integration. Test the rendered configuration using the installed SpamAssassin validation tooling and representative mail fixtures before activation. A server-level template override is not an individual mailbox preference.
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.