After
Setting up DKIM, we
have problems:
Apr 7 14:48:01 moog sendmail[22609]: t37Lm12i022609: from=, size=12316, class=-60, nrcpts=1, msgid=<
e89a8ffbab9dcca921051327938b@google.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Apr 7 14:48:01 moog sendmail[22609]: t37Lm12i022609: Milter delete: header Authentication-Results: moog.eecs.berkeley.edu;ntdkim=pass (
2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Apr 7 14:48:01 moog opendkim[7784]: t37Lm12i022609: bad signature data
Apr 7 14:48:01 moog sendmail[22609]: t37Lm12i022609: Milter insert (1): header: Authentication-Results: moog.eecs.berkeley.edu;ntdkim=
fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Apr 7 14:48:02 moog sendmail[22622]: STARTTLS=client, relay=gmail-smtp-in.l.google.com., version=TLSv1/SSLv3, verify=FAIL, cipher=ECDHE-R
SA-AES128-GCM-SHA256, bits=128/128
Apr 7 14:48:02 moog sendmail[22623]: t37Lm1w5022623: from=, size=12316, class=-60, nrcpts=2, msgid=<
e89a8ffbab9dcca921051327938b@google.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Apr 7 14:48:02 moog sendmail[22623]: t37Lm1w5022623: Milter delete: header Authentication-Results: moog.eecs.berkeley.edu;ntdkim=pass (
2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Apr 7 14:48:02 moog opendkim[7784]: t37Lm1w5022623: bad signature data
Apr 7 14:48:02 moog sendmail[22623]: t37Lm1w5022623: Milter insert (1): header: Authentication-Results: moog.eecs.berkeley.edu;ntdkim=
fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Apr 7 14:48:02 moog sendmail[22627]: t37Lm2eB022627: from=, size=12316, class=-60, nrcpts=4, msgid=<
e89a8ffbab9dcca921051327938b@google.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Apr 7 14:48:02 moog sendmail[22627]: t37Lm2eB022627: Milter delete: header Authentication-Results: moog.eecs.berkeley.edu;ntdkim=pass (
2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Apr 7 14:48:02 moog opendkim[7784]: t37Lm2eB022627: bad signature data
Apr 7 14:48:02 moog sendmail[22627]: t37Lm2eB022627: Milter insert (1): header: Authentication-Results: moog.eecs.berkeley.edu;ntdkim=
fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b=gvfaNAHW
Hmm, however, /home/mailman_7/logs/post shows it went out???
Apr 07 14:48:02 2015 (22605) post to terraswarmnews from googlealerts-noreply@google.com, size=10072, success
Anyway, here are some steps:
As root, edit /etc/opendkim.conf
## Start debugging##
# If logging is enabled, include detailed logging about why or why not a message was
# signed or verified. This causes an increase in the amount of log data generated
# for each message, so set this to No (or comment it out) if it gets too noisy.
LogWhy yes
# Instructs the filter to create temporary files containing the header and body canonicalizations of messages
# that are signed or verified. The location of these files can be set using the TemporaryDirectory parameter.
# Intended only for debugging verification problems.
KeepTemporaryFiles yes
# Specifies the directory in which temporary canonicalization files should be written. The default is to use the
# libdkim default location, currently /tmp.
TemporaryDirectory /tmp
## end debugging
To reread /etc/opendkim.conf, use kill -10 on the opendkim process.
/var/log/maillog will have
Apr 7 15:52:07 moog opendkim[7784]: configuration reloaded from /etc/opendkim.conf