- dkim2-milter: the inbound milter takes a snapshot (and stamps an
instance, and wraps) only when the chain verified or there was
none, and that snapshot is the outbound milter's proof of it. A
message whose X-DKIM2-Snapshot token names a snapshot of it is
signed without its upstream signatures being verified again:
only the Message-Instance fields are checked, with no key
lookups. The snapshot has to be of that message (the same
DKIM2-Signature fields and the instances they cover), or the
message is not signed. With no snapshot, everything is verified
before signing, as before.
- dkim2-milter: the inbound milter adds X-DKIM2-Arrival with its
verdict as one word. The outbound milter does not sign a message
that arrived fail, permerror or temperror (550 5.7.1 if it has a
DKIM2-Signature on it, as for any refusal). The field is removed
on sight by every mode, so it neither comes from outside nor
leaves the host; an inbound milter with --no-envelope-check
keeps a failing verdict the milter before it gave, and behind a
pass or none takes a Message-Instance nobody has signed for
this host's own (the m=1 the first milter stamped on an unsigned
post) instead of reporting permerror.
- Mail::DKIM2::Hop->snapshot_vouches($message, $snapshot): whether
a snapshot is of this very message.
- A message handed over as a string Perl holds as characters is
hashed as the octets those characters stand for. With the
OpenSSL digests (the default wherever Net::SSLeay is installed)
it was hashed as the string's UTF-8, so a Message-Instance
computed for such a message, if it had an octet above 0x7F in
it, did not match the octets sent. Email::MIME gives a character
string once any one header field of it has been upgraded. A
string with a character above 0xFF croaks ("Wide character"),
as it did with the CryptX digests.