I concur with Todd. Decide first what you want your sending domain to be
(hostname.domain.tld or just domain.tld). Then once you've decided on that,
stick with it (i.e. set it up on your MTA and then don't touch it) and we
can totally help you get OpenDKIM working with whichever domain name naming
scheme you want. :)
SJ
-----Original Message-----
From: tlyons_at_sitehelp.org [mailto:tlyons_at_sitehelp.org] On Behalf Of Todd
Lyons
Sent: Tuesday, October 26, 2010 3:51 PM
To: Jason Clint
Cc: steve_at_stevejenkins.com; opendkim-users_at_lists.opendkim.org
Subject: Re: Signing problem
On Tue, Oct 26, 2010 at 3:39 PM, Jason Clint <nosaj_17_at_hotmail.com> wrote:
> Message contains this DKIM Signature:
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
> d=mail.marlborosurvey.net; s=mail; t=1288132621;
Note the domain is mail.marlborosurvey.net, so that means domainkey
stuff will be looked for under _domainkey.mail.marlborosurvey.net,
*NOT* _domainkey.marlborosurvey.net. You need to adjust your dns to
make this configuration work.
> Public Key DNS Lookup
>
> Building DNS Query for mail._domainkey.mail.marlborosurvey.net
> Retrieved this publickey from DNS:
>
> Validating Signature
>
> result = invalid
> Details: public key: not available
admin51 ~ # dig +short -t txt mail._domainkey.mail.marlborosurvey.net
admin51 ~ # dig +short -t txt mail._domainkey.marlborosurvey.net
"v=DKIM1\; k=rsa\;
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGAq3ldG6D1fJiWoXPDpKg9dx42LhQysLAgM
wo7cDrBiPMJ9jKh/YIAPAdFm6lHMWOQiL+IryQH+XCMSecdEj67Uw+EIxMgVT/KNQAH9Lqax8YnM
5f91XZrazHLfa8U+bzHrSw15VhXCe9wb+sDtSa3E39naEY7nW5EJRCnCEm0QIDAQAB"
Your DNS requires adjustment.
--
Regards... Todd
I seek the truth...it is only persistence in self-delusion and
ignorance that does harm. -- Marcus Aurealius
Received on Tue Oct 26 2010 - 22:53:26 PST