- Implemented support for Canonicalization option
- Implemented support for SyslogFacility option - Initial dataset support: csl - Only sign if mail from from a domain in Domain and only if Mode is not verfication only - Fixed Canonicalize option
This commit is contained in:
+9
-10
@@ -152,13 +152,12 @@ a milter-aware MTA.
|
||||
.SH DATA SETS
|
||||
Many of the configuration file parameters will refer to a "dataset" as their
|
||||
values. This refers to a string that either contains the list of desirable
|
||||
values, or to a file that contains them, or (if enabled at compile time) a
|
||||
database containing the data.
|
||||
values, or to a file that contains them, or a database containing the data.
|
||||
|
||||
Some data sets require that the value contain more than one entry. How this
|
||||
is done depends on which data set type is used. Not all these datasets are
|
||||
currently used by dkimp-milter. See
|
||||
.B opendkim-milter.conf(5)
|
||||
.B dkimpy-milter.conf(5)
|
||||
for details about specific options and which dataset types they use.
|
||||
|
||||
In particular:
|
||||
@@ -170,7 +169,7 @@ one per line. If a line contains whitespace-separated values, then the
|
||||
line is presumed to define a key and its corresponding value. Blank lines
|
||||
are ignored, and the hash ("#") character denotes the start of a comment.
|
||||
If a value contains multiple entries, the entries should be separated by
|
||||
colons.
|
||||
colons. [Not implemented yet]
|
||||
.TP
|
||||
.I b)
|
||||
If the string begins with "refile:", then the remainder of the string is
|
||||
@@ -180,7 +179,7 @@ to the first whitespace, and the portion after that whitespace is taken as
|
||||
the value to be used when that pattern is matched. Patterns are simple
|
||||
wildcard patterns, matching all text except that the asterisk ("*") character
|
||||
is considered a wildcard. If a value contains multiple entries, the entries
|
||||
should be separated by colons.
|
||||
should be separated by colons. [Not implemented yet]
|
||||
.TP
|
||||
.I c)
|
||||
If the string begins with "db:" and the program was compiled with
|
||||
@@ -188,24 +187,24 @@ Sleepycat DB support, then the remainder of the string is presumed to
|
||||
identify a Sleepycat database containing keys and corresponding values.
|
||||
These may be used only to test for membership in the data set, or for
|
||||
storing keys and corresponding values. If a value contains multiple entries,
|
||||
the entries should be separated by colons.
|
||||
the entries should be separated by colons. [Not implemented yet]
|
||||
.TP
|
||||
.I h)
|
||||
If the string contains none of these prefixes but ends with ".db", it
|
||||
is presumed to be a Sleepycat DB as described above (if support for same
|
||||
is compiled in).
|
||||
is compiled in). [Not implemented yet]
|
||||
.TP
|
||||
.I i)
|
||||
If the string contains none of these prefixes but starts with a slash ("/")
|
||||
character, it is presumed to be a flat file as described above.
|
||||
character, it is presumed to be a flat file as described above. [Not implemented yet]
|
||||
.TP
|
||||
.I j)
|
||||
If the string begins with "csl:", the string is treated as a comma-separated
|
||||
list as described in m) below.
|
||||
list as described in m) below. [Not implemented yet]
|
||||
.TP
|
||||
.I l)
|
||||
If the string begins with "mdb:", it refers to a directory that contains
|
||||
a memory database, as provided by libmdb from OpenLDAP.
|
||||
a memory database, as provided by libmdb from OpenLDAP. [Not implemented yet]
|
||||
.TP
|
||||
.I m)
|
||||
In any other case, the string is presumed to be a comma-separated list.
|
||||
|
||||
Reference in New Issue
Block a user