Hector Santos skrev den 2016-11-02 21:05:
ADSP/ATPS actually works very well. Its been in production for a
number of years. I have "ietf.org" as a 3rd party signer assigned to
my ATPS records in DNS. Supportive receivers can then see that I
authorize ietf.org to sign my IETF submissions as my receivers do when
I get a copy. My ADSP record for isdg.net is:
dkim=all; atps=y;
asl=ietf.org,beta.winserver.com,santronics.com,isdg.net,winserver.com,megabytecof
fee.com,mapurdy.com.au,mipassoc.org,gmail.com,googlegroups.com;"
Authentication-Results: linode.junc.eu; dmarc=none header.from=isdg.net
Authentication-Results: linode.junc.eu;
dkim=pass (1024-bit key; secure) header.d=ietf.org header.i=@ietf.org
header.b=vqpaROA9;
dkim=fail reason="signature verification failed" (1024-bit key;
unprotected) header.d=isdg.net header.i=@isdg.net header.b=twhXt8L/;
dkim=fail reason="signature verification failed" (1024-bit key;
unprotected) header.d=beta.winserver.com header.i=@beta.winserver.com
header.b=ubq9bnhD;
dkim-atps=neutral
so it works ?
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc
