-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In message <[email protected]>, Steven M Jones <[email protected]> writes
>If I follow this, the use case is a Secure Email Gateway or SEG, to use a >Gartner-ism, and is likely the last hop before delivery to the recipient ADMD >or >mailstore. So why is DKIM2's "it's complicated" flag more useful here than the >configured exception for the service or gateway the receiving ADMD contracted >with? it means that if the message, for whatever reason, reaches another DKIM2 system it is possible to determine that the gateway intentionally changed the message ... (and hence local policy is going to have to kick in to decide what to do with a failing signature) otherwise one might conclude that the failure of every preceding signature was some other systems failure to look after the message properly -- and it might be that a DSN was speciously generated (depending on the exact chain of custody) - -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBZz1Rgt2nQQHFxEViEQLxbQCgqj//0vmL3p8BevIEvJXgVwABM1sAoMAB 4H1Lz7T3uxZxpa+qVc7CG59A =WV24 -----END PGP SIGNATURE----- _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
