Also, I have no idea what all of the addresses are that I've made up
over the years, many of which still get mail from whoever I gave them
to. It appears I'm out of luck there.
For one, you can do *._openpgpkey.example.com. IN OPENPGPKEY [...]
My system has more than one user, so we have addresses like johnl-*
bobf-*. How are we supposed to handle that with DNS wildcards?
Second you should really have the email address listed as ID on you
openpgp key entry anyway.
I do, and thousands of subaddresses, too, and I'd like to let people send
me mail just like they do now, only encrypted.
Third, you can keep doing this fine and not receive encrypred email,
just like you have been doing all of those years.
I'm not very interested in a "solution" that doesn't match the way e-mail
works, and has worked for decades. At the session in Dallas, it was
pretty clear that the other people at the mike with extensive e-mail
experience aren't either.
This is starting to remind me of too many other discussions of mail
security hacks that don't match the way that mail actually works, in which
the propnents argue that the parts of our working mail that don't happen
to match the hack was broken all along. (See, for example, endless
arguments about "forgery" in SPF and DMARC lists.)
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
