Eliot Lear wrote: > Can someone please explain how something can be opaque and yet processed > in g=, as SM has pointed out?
1. g= provides a literal string for comparison. It does not specify any other syntax or semantics for the string. Hence, the string cannot be interpreted. It can only be compared, which means the string is opaque. 2. g= is for a mechanism that is internal to the dkim signature processing engine. It does not impart any syntax or semantics if the target string is output to a client of the signature validation process. To the module that consumes that string, as output of DKIM validation, the string remains opaque. DKIM imparts and communicates no details about the meaning of the string, nor its relationship to other identifiers. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
