Stepping back for a moment...is there any reason that the identifier
can't be 'icannhascheezburger' or some other nonsense, so long as the
internal network (and perhaps MUAs which connect to that internal
network) knows what to look for?
Within a given network the identifier doesn't matter, but I think it'd
be a good idea if the identifiers applied by different networks didn't
collide so my gateway scenario will work.
Something similar to the rules for generating a Message-ID should do
the trick, the name can be arbitrary so long as it's in a domain you
control.
R's,
John
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html