It appears that Bron Gondwana <[email protected]> said: >-=-=-=-=-=- > >Surely you'd just wrap the entire DKIM2-signed email with encryption? If not, >then you're either creating a brand new email and your >gateway is implicitly trusted, so NULL recipe or just an >Authentication-Results header and no DKIM2 at all. >...
Pretty close. >And you can't be an encryption gateway in the middle of a mail flow between >unrelated parties. What even is that. If you don't have a >relationship with either the sender or the recipient, then who verifies the >legitimacy of the keys you're using? One can publish a public key that strangers use to send you mail that only you can decode. PGP and S/MIME both allow it and I get a trickle of mail like that. The gateway need not have a relationship with either end, but it can't just mechanically wrap and relay everthing it gets or spammers will abuse it and recipients will block it as a spam relay. But you can't do useful spam filtering without looking inside the message, so the only plausible approach is what Bron said, use the encrypted message as a tunnel and the recipient checks the DKIM2 chain after it unwraps it. And you better do some heavy filtering before you encrypt and relay or nobody's going to be willing to unwrap it. R's, John PS: This is a hard problem, which is one of the reasons you don't see any gateways like this outside of very narrow niches. _______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
