OpenDKIM charm.
Channel | Revision | Published | Runs on |
---|---|---|---|
2/edge | 7 | Today |
juju deploy opendkim --channel 2/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
keytable | string
Key table mapping. This configuration is in YAML format. It is a list of lines, being each line another list with two elements, the key and the value. The following is an example of a keytable:
- - "selector._domainkey.example.com - "example.com:selector:/etc/dkimkeys/key1.private" - - "selector._domainkey.other.example.com" - "other.example.com:selector:/etc/dkimkeys/key2.private"
-
mode | string
Default: sv
Selects operating modes. The string is a concatenation of characters that indicate which mode(s) of operation are desired. Valid modes are s (signer) and v (verifier). The default is sv
See http://www.opendkim.org/opendkim.conf.5.html
-
private-keys | secret
Secret that contains the private keys. The keys in the secret define the filename without the '.private' extension, and the value the private key.
-
signingtable | string
Signing table mapping. This configuration is in YAML format. It is a list of lines, being each line another list with two elements, the key and the value. The file format is refile, so it can include regular expressions. The folloging is an example of the signingtable:
- - "*@example.com" - "selector._domainkey.example.com" - - "*@other.example.com" - "selector._domainkey.other.example.com"