Closed dilyanpalauzov closed 6 years ago
even if it seem to be retundant: explicit mention the default is good practice
For other booleans nothing explicit is said about the default value, hence right now it is inconsistent. If the default values are stated explicitly, then this has to be done everywhere, and the clarification for implicit false boolean, unless otherwise stated, removed.
in that sense you're right. Defaults should be states for all options could that issue be tagged as feature request and be renamed?
I consider both changing the subject and tagging for insignificant here.
The description says Boolean values default to "false". It is redundant to state that the defaults for DomainKeyCompat and ResignAll are false.
MinimumKeysBits states "The default is 1024, which accepts all signatures. A value of 0 causes the default to be used." There are 768bit signatures today, so that 0 means indeed all signatures are checked, but 1024 -the default - does not mean that all signatures are checked.
ReplaceRule states 'This can be used to accommodate expected changes such as are made to From: fields by MTA "masquerade" features.' -- needs rephrasing.
ScreenPolicyScript states "The script has access to all of the header fields and connection information and can that certain signatures be ignored based on that information." This needs rephrasing.
TemporaryDirectory speaks about libdkim but means libopendkim.
Copy of https://sourceforge.net/p/opendkim/bugs/263/.