←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.198s | 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. leakycap ◴[30 Jun 25 08:46 UTC] No.44420930[source]▶
It is easy to think something like this is easy until you attempt to do it.

Are you really questioning a free SSL Certificate system when it says something is too complex and not worth it?

If you ever set up a free SSL before LetsEncrypt, you'd know they're amazing and you can trust them not to lie to you, especially about this where they've outlined the reasons clearly.