On Tue, Jul 17, 2012 at 02:21:50PM +0530, Naval saini wrote:
> This is my DNS ZONE file entry:
>
> _domainkey.r02.lbsmtp.org. IN TXT "t=y; o=-;"
The above resource record (RR) has no selector, it has no meaning in DKIM.
> lbsmtp.org._domainkey.r02.lbsmtp.org. IN TXT
> "k=rsa; t=y;
> p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC+Nk+qAXShe92GLTe8sXXHFeH+
> lqZpxWMqCPqRdowGTx3Scrq7mgqEPnc49Po5cS0NjZI/eWF/rzD7/qpbpKLR2eZx
> 3/8JEn67EtjKmuVc/uyejL5WSxkHsj4rhHFnX96yqV0iS+odGqy4c/QWvbbF+LB/
> rcOXDkvOR544O4LGgwIDAQAB"
Congratulations, you're configured a 1024-bit RSA key (many sites have
foolishly created 512-bit RSA keys, which are too easily factored). That
said, your DNS does not in fact publish this RR to the world at large:
$ dig -t txt lbsmtp.org._domainkey.r02.lbsmtp.org
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18036
lbsmtp.org. 7200 IN SOA enow.mercury.orderbox-dns.com. ...
So your DKIM public key is not available for verification. Over
and out.
--
Viktor.
