Created
February 24, 2010 17:07
-
-
Save cromulus/313623 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Log to syslog | |
Syslog yes | |
# Required to use local socket with MTAs that access the socket as a non- | |
# privileged user (e.g. Postfix) | |
UMask 108 | |
# Sign for example.com with key in /etc/mail/dkim.key using | |
# selector '2007' (e.g. 2007._domainkey.example.com) | |
Domain mailer.headliner.fm | |
KeyFile /etc/mail/domainkey.key | |
Selector 2007 | |
# Common settings. See dkim-filter.conf(5) for more information. | |
AutoRestart yes | |
Background yes | |
Canonicalization simple | |
DNSTimeout 5 | |
Mode sv | |
SignatureAlgorithm rsa-sha256 | |
SubDomains yes | |
#UseASPDiscard no | |
#Version rfc4871 | |
X-Header yes | |
InternalHosts /etc/mail/dkim-InternalHosts.txt | |
############################################### | |
# Other (less-standard) configuration options # | |
############################################### | |
# | |
# If enabled, log verification stats here | |
Statistics /var/log/dkim-filter/dkim-stats | |
# | |
# KeyList is a file containing tuples of key information. Requires | |
# KeyFile to be unset. Each line of the file should be of the format: | |
# sender glob:signing domain:signing key file | |
# Blank lines and lines beginning with # are ignored. Selector will be | |
# derived from the key's filename. | |
#KeyList /etc/dkim-keys.conf | |
# | |
# If enabled, will generate verification failure reports for any messages | |
# that fail signature verification. These will be sent to the r= address | |
# in the policy record, if any. | |
#ReportInfo yes | |
# | |
# If enabled, will issue a Sendmail QUARANTINE for any messages that fail | |
# signature verification, allowing them to be inspected later. | |
#Quarantine yes | |
# | |
# If enabled, will check for required headers when processing messages. | |
# At a minimum, that means From: and Date: will be required. Messages not | |
# containing the required headers will not be signed or verified, but will | |
# be passed through | |
#RequiredHeaders yes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment