依田 邦章 wrote: > >> As Ben correctly indicated, this will sign your mail with "s=test" and >> "d=hoge.com" which will cause verifiers to look to >> "test._domainkey.hoge.com" for your public key. However, that record >> doesn't appear to exist. This will (obviously) prevent successful >> validations. >> >> >>> # dns >>> test._domainkeyi.hoge.com. IN TXT "v=DKIM1; g=*; k=rsa; t=s; p=MIGf・・・AB" >>> >>> >> As Ben also indicated that "i" could be the problem. >> >>> _policy._domainkey.hoge.com. IN TXT "t=y; o=~" >>> > it's correct dns zone file. > however, it doesn't move still well. > It's still not visible in your DNS from here:
% host -t txt test._domainkey.hoge.com. Host not found. If I can't get your key, I can't verify your signatures. Looks like there's something you need to fix on your end with the DNS setup. > is the way of making my key bad? > /usr/bin/dkim-genkey -d hoge.com -r -s test > > Looks fine to me. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
