←back to thread

LetsEncrypt – Expiration Notification Service Has Ended

(letsencrypt.org)
181 points zdw | 2 comments | 30 Jun 25 04:49 UTC | HN request time: 0.539s | source
Show context
wordofx[dead post] ◴[30 Jun 25 07:41 UTC] No.44420535[source]▶
[flagged]
gleenn ◴[30 Jun 25 08:28 UTC] No.44420820[source]▶
Sending single custom emails is much more effort than bulk-mailing a huge list operationally. Sending bulk can be accomplished by uploading a csv of emails to some enail bulk sender versus code to run at the correct time for the correct user... way easier in bulk and way cheaper
replies(2): >>44420845 #>>44421262 #
wordofx ◴[30 Jun 25 09:37 UTC] No.44421262[source]▶
It has nothing to do with complexity.

> Providing expiration notification emails means that we have to _retain millions of email addresses_ connected to issuance records. As an organization that _values privacy_, removing this requirement is important to us.

A mailing list. Is still retaining emails somewhere. Doesn’t matter if it’s stored in a text file on a usb drive in a vault. It’s still retaining an email list.

replies(1): >>44422109 #
1. nulbyte ◴[30 Jun 25 11:46 UTC] No.44422109[source]▶
I think the key part is what you didn't emphasize: "connected with issuance records." A list of email addresses is just a list of email addresses. A list of email addresses with domains over which the recipient has control is far more interesting data.
replies(1): >>44427067 #
2. wordofx ◴[30 Jun 25 19:42 UTC] No.44427067[source]▶
Irrelevant.