Name: opendkim-signer
Owner: Discourse
Description: null
Created: 2018-02-06 17:26:48.0
Updated: 2018-05-15 05:05:13.0
Pushed: 2018-05-15 05:05:12.0
Homepage: null
Size: 5
Language: Shell
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This container is about as stupidly simple a DKIM signer as is possible: for
every message received on whatever socket you specify with the
MILTER_SOCKET environment variable (using the milter protocol), it signs
the message using the specified private key, with the domain (d=) and
selector (s=) parameters given in the relevant environment variables.
That's it.
Mount a volume somewhere that contains the private key you want to use for signing, then specify the key file's location, along with the desired domain and selector, using env vars. Also, specify a milter socket location so that your MTA can get the messages to the DKIM server.
Instances of this image require the following environment variables to be set in order for things to work:
DKIM_KEY_FILE – the fully-qualified filename of the PEM-formatted
private key to use to sign all e-mail that comes through this instance.
This will point to wherever you mounted the private key to use.
DKIM_SELECTOR – the short, unique string to use as the “DKIM selector”
on all mail signed by this instance. This needs to line up with the DNS
records you created.
SIGNING_DOMAIN – the domain to specify as the “signing domain” on all
mail.
MILTER_SOCKET – the value for the Socket parameter in
opendkim.conf. You probably want to read the opendkim.conf manpage to find out exactly
what is legal here.
Running make will build and push.