On 04/22/14 13:01, Murray S. Kucherawy wrote:
> opendkim relies on resolver libraries to go get the data, and one of them
> is telling opendkim that the key isn't there. There's likely nothing in
> opendkim to debug.
OK, nothing internal to opendkim then. Just straight DNS.
> Assuming the details in your opendkim.conf are
> current, I can't resolve it even from the command line here:
>
> % host -t txt dkim._domainkey.caerllewys.net
> Host dkim._domainkey.caerllewys.net not found: 3(NXDOMAIN)
OPK, I'll have to doublecheck the TXT record definition *again* and make
sure I didn't miss anything.
>> ExternalIgnoreList babcom.com
>
> But the host that connected is babylon5.babcom.com. As specified, only a
> direct string match will be considered a hit.
Doh! *facepalm* I didn't realize that it was matched that way.
Edited, and thanks.
--
Phil Stracchino
Babylon Communications
phils_at_caerllewys.net
phil_at_co.ordinate.org
Landline: 603.293.8485
Received on Tue Apr 22 2014 - 18:49:04 PST