------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1574
Summary: Config syntax check fails as part of ansible deployment
Product: Exim
Version: N/A
Platform: Other
OS/Version: All
Status: NEW
Severity: wishlist
Priority: medium
Component: General execution
AssignedTo: nigel@???
ReportedBy: daniel@???
CC: exim-dev@???
The canonical way to check the syntax of an exim configuration before putting
it live is "exim -C /path/to/config -bV" and testing for a 0 exit status. As
part of this, recent exim versions complain about wrong owner and permissions
if the file has owner or permissions different from what exim expects. However,
when checking syntax as part of automated configuration deployment e.g. using
ansible, it is not uncommon that the configuration file before installation is
owned by a different user or has different permissions. This happens e.g. when
using ansible with a sudo configuration and using the validate= ansible feature
to check syntax of the configuration before deploying it. As a result,
ansible's validate= cannot be used with exim's -C -bV combo.
While the check for correct owner and permissions is reasonable at runtime,
there should be a way to check an arbitrary exim configuration file for syntax
errors without doing the owner and permission checks.
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
