Ending Support for Expiration Notification Emails
letsencrypt.org
Since its inception, Let’s Encrypt has been sending expiration notification emails to subscribers that have provided an email address to us. We will be ending this service on June 4, 2025. The decision to end this service is the result of the following factors: Over the past 10 years more and more of our subscribers have been able to put reliable automation into place for certificate renewal. Providing expiration notification emails means that we have to retain millions of email addresses connected to issuance records.

I think it’s a good idea, everyone should be automating this anyway.

  • cm0002@lemmy.worldEnglish
    3·
    13 hours ago

    still want to make sure even on my private network I’m using valid certs. A lot of security departments require that too even if the device isn’t public facing.

    Is there a hard source with evidence that this is at all needed? Because there are a lot of things that “security departments” do that amount to security theater. Like forcing arbitrary password changes org wide.

    • ramble81@lemm.eeEnglish
      3·
      13 hours ago

      Regardless of “hard evidence” it’s still the company policy. How well does it go over if you try to say “well acktuslly…” when it comes to password changes.

      • cm0002@lemmy.worldEnglish
        4·
        13 hours ago

        How well does it go over if you try to say “well acktuslly…” when it comes to password changes.

        Well, it went over easy, but I also gained the authority to implement or toss such policies when I took my job LMAO

        In any case, I was referring to the “my environment” part since it implied you had such authority and were just choosing to emulate policies of others, ofc I don’t mean to make decisions you don’t have the authority to. Hard evidence is hard evidence though, it does give you a leg to stand on should you propose such changes