Re: [Endymail] Hashes of key as addresses

[Steffen Nurpmeso <[e-mail]>]

 |As it stands, with SMTP, assuming transport security (_proper_
 |STARTTLS, for example)

I don't know how many messages are sent over SMTP each day, but it
would be interesting to know how much energy all those useless
roundtrip packets consume which are necessary to get upgrade
a SMTP session via STARTTLS, and how many percent of those
connections could also instantiate a non-existent SMTPS instead,
not requiring these upgrades.
Imagine all those billion indic kids treadle the dynamos to
produce the necessary electricity; granted it improves the
quality of their organs, too, so win-win here.

And in my world there was no support for DNSSEC, but omnipresent
support for TLS over TCP.  It would take a day to extend the
resolver, with fewest additional code, based on external
crypto / ssl/tls libraries which get used trillion times each day.
And with a caching resolver and/or a local DNS cache that
additional cost on the DNS side would be balanced out by the
savings of the much more often occurring SMTPS connections.
Oh well, it is much too late for this nagging, of course.
And there are really some domains which use DNSSEC today; my bank
does not however, and unfortunately ;-))  But of course their
website is protected via https, after so much phishing, ..say.
I wonder wether that sorts out the problem.

--steffen