> From: "Gellner, Oliver" > when I grep Microsoft DMARC reports for temperror, there are hundreds of > hits. Nevertheless I don't see why you should change your policy because > one recipients is unable to reliably operate a DNS client.
> <domain>dm-jobs.com</domain> > <selector>dmglobal4</selector> > <result>temperror</result> > </dkim> ~ $ time dig +trace dmglobal4._domainkey.dm-jobs.com txt dmglobal4._domainkey.dm-jobs.com. 86400 IN CNAME dmglobal4._domainkey.dm.de. real 0m1,337s ~ $ time dig +trace dmglobal4._domainkey.dm.de txt dmglobal4._domainkey.dm.de. 86400 IN TXT "v=DKIM1; h=sha256; t=s; p=MI... real 0m0,869s Total over 2 sec. May be too short timeout? + more compicated DNS (with CNAME). For comparison, my domain 5._domainkey.lena.kiev.ua (without CNAME): real 0m0,210s _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
