DandelionNStuff/dkimpy-milter-smtputf8
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move Diagnostics option to initial beta release plan and add to dkimpy-milter.conf.5

Browse Source
This commit is contained in:
Scott Kitterman
2018-02-16 16:22:44 -05:00
parent 3e032ad6ad
commit 45bc88e5e9
2 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODO
+3 -3
View File
@@ -17,9 +17,11 @@ UserID implemented verified
0.9.5 (Beta) 0.9.5 (Beta)
AuthservID AuthservID
Canonicalization Canonicalization
Diagnostics
DiagnosticDirectory DiagnosticDirectory
InternalHosts InternalHosts
SyslogFacility SyslogFacility
SyslogSuccess
1.0.0 1.0.0
No additional features planned No additional features planned
@@ -29,14 +31,12 @@ Considered for near-term feature release
AlwaysAddARHeader AlwaysAddARHeader
ChangeRootDirectory ChangeRootDirectory
ClockDrift (requires dkimpy change) ClockDrift (requires dkimpy change)
Diagnostics DNSTimeout (requires dkmpy change)
DNSTimeout (required dkmpy change)
MacroList MacroList
MilterDebug MilterDebug
MinimumKeyBits MinimumKeyBits
PeerList PeerList
SignatureAlgorithm SignatureAlgorithm
SyslogSuccess
Later Later
dkimpy-milter.conf.5
+7
View File
@@ -213,6 +213,13 @@ The value may include two different canonicalizations separated by a
slash ("/") character, in which case the first will be applied to the slash ("/") character, in which case the first will be applied to the
header and the second to the body. header and the second to the body.
.TP
.I Diagnostics (Boolean)
Requests the inclusion of "z=" tags in signatures, which encode the
original header field set for use by verifiers when diagnosing verification
failures. Not recommended for normal operation. [dkimpy-milter specific: also
increases the verbosity of Syslog logging if enabled.]
.TP .TP
.I DiagnosticDirectory (string) .I DiagnosticDirectory (string)
Directory into which to write diagnostic reports when message verification Directory into which to write diagnostic reports when message verification