←back to thread

LetsEncrypt – Expiration Notification Service Has Ended

(letsencrypt.org)
181 points zdw | 1 comments | 30 Jun 25 04:49 UTC | HN request time: 0.216s | 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 #
Y_Y ◴[30 Jun 25 08:32 UTC] No.44420845[source]▶
Is it truly much more difficult? At worst you could batch them by week and registered email, a one-liner can generate the list of destinations, and then you send that to your newsletter-sender-service and call the email "your cert is expiring next week".
replies(2): >>44420930 #>>44421142 #
1. szszrk ◴[30 Jun 25 09:17 UTC] No.44421142[source]▶
Of course it's more difficult.

You are talking of a volume of around 600 000 000 domains (based on a plot on their website) that try to renew at best after 8 weeks. And that's just default profile, there are 160h certs profiles now [0].

You think they will ever send nearly as much as (at least) 75 million newsletter mails weekly? Sendgrid's highest value in their pricing slider is 1,25 mil a week.

- [0] https://letsencrypt.org/docs/profiles/