Jim,
That is the same key record that is used by Yahoo (since they send for
sbcglobal.net). Are you having similar problems on yahoo.com messages?
Otherwise it might be work checking to see what's different between
yahoo.com and sbcglobal.net.
Thinking more broadly (including dkim-milter as well), I'm wondering if
the defaults for -C should be adjusted to accept the message in nearly
all cases. The only really legitimate tempfail case is if the milter
gets a temporary error (i.e., not NXDOMAIN or "nodata" response) when
retrieving the key. In other cases, it's very unlikely that tempfailing
the message is going to do any good. It just delays the inevitable for a
few days unless some unusually-vigilant sysadmin notices messages in the
queue and investigates.
-Jim (F)
Jim Hermann - UUN Hostmaster wrote:
> Murray,
>
> This problem continues to this day:
>
> s1024._domainkey.sbcglobal.net. 1182 IN TXT "k=rsa\; t=y\;
> p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDrEee0Ri4Juz+QfiWYui/E9UGSXau/2P8Ljn
> TD8V4Unn+2FAZVGE3kL23bzeoULYv4PeleB3gfm"
> "JiDJOKU3Ns5L4KJAUUHjFwDebt0NP+sBK0VKeTATL2Yr/S3bT/xhy+1xtj4RkdV7fVxTn56Lb4u
> dUnwuxK4V5b5PdOKj/+XcwIDAQAB\; n=A 1024 bit key\;"
>
> Mar 4 15:17:14 host dk-filter[19866]: n24LHDRR017696: dk_eom(): internal
> error from libdk: DNS reply for `s1024._domainkey.sbcglobal.net' truncated
>
> I am running dk-milter-1.0.1 compiled with libar on Fedora Core 4.
>
> Jim
>
>
>> -----Original Message-----
>> From: Murray S. Kucherawy [mailto:msk@...]
>> Sent: Friday, December 05, 2008 12:09 AM
>> To: General discussion and usage issues
>> Subject: Re: dk_eom(): internal error from libdk: DNSreply
>> for`s1024._domainkey.sbcglobal.net' truncated
>>
>> Jim Hermann - UUN Hostmaster wrote:
>>
>>> I'm having another internal error from libdk.
>>>
>>> This is the DNS Record:
>>>
>>> s1024._domainkey.sbcglobal.net. 1193 IN TXT "k=rsa\; t=y\;
>>>
>>>
>> p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDrEee0Ri4Juz+QfiWYui/E
>> 9UGSXau/2P8Ljn
>>
>>> TD8V4Unn+2FAZVGE3kL23bzeoULYv4PeleB3gfm"
>>>
>>>
>> "JiDJOKU3Ns5L4KJAUUHjFwDebt0NP+sBK0VKeTATL2Yr/S3bT/xhy+1xtj4Rk
>> dV7fVxTn56Lb4u
>>
>>> dUnwuxK4V5b5PdOKj/+XcwIDAQAB\; n=A 1024 bit key\;"
>>>
>>>
>> I concocted a message signed such that it would retrieve and process
>> that key and got no errors. Can you send me a sample message which
>> causes this problem?
>>
>> This is still the d2i_PUBKEY_bio() error you were referring
>> to earlier?
>>
>>
|