#70 Fail if configuration is invalid

[A. Schulze]

2.3.1 will Fix the bug #SF3196069: Log more detail when dkimf_config_setlib() fails.
an unbound.conf which is unreadable for the user opendkim runs as produces an informal warning.

After this warning opendkim works as usual and verify correctly but do not honor any dnssec related settings.

... but operation will FAIL if opendkim is running on a system which *must* use a dedicated dns forwarding
resolver. In this case is may be better not to continue.

So maybe it is better to stop working, if configured files are unaccessible or contain invalid content.
This whoud force an admin to fix the problem rather then running a software with unintended behavior.

Andreas

[Murray S. Kucherawy]

This requires some untangling. The config objects make use of (unfortunately shared) global objects like the unbound handle. For this to be fixed, rollback has to be possible, which means we'll need an unbound/arlib handle for each config object.

[Murray S. Kucherawy]

Done for 2.3.2.

[Murray S. Kucherawy]

Fix for this bug included in new release.