RE: QUERY: Key Server Choices

If that's really it, then my current implementation would see 
q=xkms and 
set:

Authentication-Results: dkim=neutral

I assume that you agree that my implementation is correct.


Provided that is consistent with the policy record. IE if the policy
record says that every message is signed with q=dns then q=xkms is an
error.

Otherwise you are right.

<Prev in Thread]	Current Thread	[Next in Thread>
Re: QUERY: Key Server Choices, (continued) Re: QUERY: Key Server Choices, Michael Thomas Header field canonicalzation question, Bryan Costales Re: Header field canonicalzation question, Arvel Hathcock Re: Header field canonicalzation question, Arvel Hathcock Re: QUERY: Key Server Choices, william(at)elan.net Re: QUERY: Key Server Choices, wayne Re: QUERY: Key Server Choices, Earl Hood Re: QUERY: Key Server Choices, Arvel Hathcock RE: QUERY: Key Server Choices, Hallam-Baker, Phillip Re: QUERY: Key Server Choices, Michael Thomas RE: QUERY: Key Server Choices, Hallam-Baker, Phillip <= RE: QUERY: Key Server Choices, James Scott RE: QUERY: Key Server Choices, domainkeys-feedbackbase02 The cost of choices, Dave Crocker Re: The cost of choices, william(at)elan.net Re: The cost of choices, Hector Santos Re: The cost of choices, Arvel Hathcock Re: QUERY: Key Server Choices, Hector Santos Re: QUERY: Key Server Choices, Thomas Roessler Message not available RE: QUERY: Key Server Choices, SM RE: QUERY: Key Server Choices, Hallam-Baker, Phillip

Previous by Date:	Re: QUERY: Key Server Choices, Michael Thomas
Next by Date:	RE: QUERY: Key Server Choices, James Scott
Previous by Thread:	Re: QUERY: Key Server Choices, Michael Thomas
Next by Thread:	RE: QUERY: Key Server Choices, James Scott
Indexes:	[Date] [Thread] [Top] [All Lists]