# Missing expiration note email

**URL:** <https://community.letsencrypt.org/t/missing-expiration-note-email/160457>\
**Category:** Help\
**Created:** [September 25, 2021, 8:50am UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457 "2021-09-25T08:50:58Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zulan](https://avatars.discourse-cdn.com/v4/letter/z/bbe5ce/32.png) [@Zulan](https://community.letsencrypt.org/u/Zulan)\
**Post date:** [September 25, 2021, 8:50am UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/1 "2021-09-25T08:50:58Z")

</div>

Normally I get expiration note emails 20 days and then if I don't renew already 10 days before expiration.  
However, this morning, I received the first expiration note 2 hours before expiration. I thoroughly searched all my email folders and definitely did not _receive_ an email for this specific expiration date before.

My domain is:

[zulan.net](http://zulan.net)

I have two groups of domains on two hosts that I renew separately and get separete emails for. Both are equally affected.

I am fairly sure that my email-system was working to receive emails continuously and can pretty much rule out it eating 2x2 emails 10 days apart.

Was there a known issue with the Let's encrypt emailing? What else could have caused this? How can I avoid that in the future?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [September 25, 2021, 1:10pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/2 "2021-09-25T13:10:30Z")

</div>

Hi @Zulan, welcome to the LE community forum 🙂

> [@Zulan](#):
>
> Was there a known issue with the Let's encrypt emailing?

Yes; there was an email issue recently and it ~~has been corrected~~ is being dealt with.

> [@Zulan](#):
>
> How can I avoid that in the future?

I would try to automate the renewals before any expiry email is sent.  
To that end, why aren't your certs being renewed automatically before the expiry emails are sent?  
Perhaps that is something we can help you with here.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [September 25, 2021, 1:41pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/3 "2021-09-25T13:41:04Z")

</div>

> [@rg305](#):
>
> and it has been corrected

Was it?

That issue was about sending expiration emails for already renewed certs. Although the issue about _not_ sending expiry emails is _known_ with the staff, I have not seen any issue on the Boulder github page nor have I seen anything mentioned about it being fixed.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [September 25, 2021, 1:49pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/5 "2021-09-25T13:49:23Z")

</div>

It seems _you may be right - I may be crazy!_  
There were two ongoing email issues and only one has been explicitly corrected.  
We may have to wait a bit to see if this other issue still remains.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [September 25, 2021, 1:49pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/6 "2021-09-25T13:49:39Z")

</div>

See here: [https://community.letsencrypt.org/t/emails-gone-wild/160153/10?u=osiris](https://community.letsencrypt.org/t/emails-gone-wild/160153/10)

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [September 25, 2021, 1:52pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/7 "2021-09-25T13:52:08Z")

</div>

@Osiris, You are too funny!  
[that is a topic I opened]

---

<div class="post-metadata">

**Author:** ![jcjones](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jcjones/32/78_2.png) [@jcjones](https://community.letsencrypt.org/u/jcjones)\
**Post date:** [September 25, 2021, 2:06pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/8 "2021-09-25T14:06:15Z")

</div>

> [@Osiris](#):
>
> That issue was about sending expiration emails for already renewed certs. Although the issue about _not_ sending expiry emails is _known_ with the staff, I have not seen any issue on the Boulder github page nor have I seen anything mentioned about it being fixed.

That's right, the incorrect data issue -- which prompted us to stop the mailer for most of the week -- is fixed. However, the mailer has had a different issue where it isn't always able to send the emails on time. That issue doesn't yet have a root cause, but I have some changes in flight (going to Staging on Monday) that might help it.

---

<div class="post-metadata">

**Author:** ![Zulan](https://avatars.discourse-cdn.com/v4/letter/z/bbe5ce/32.png) [@Zulan](https://community.letsencrypt.org/u/Zulan)\
**Post date:** [September 25, 2021, 2:11pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/9 "2021-09-25T14:11:19Z")

</div>

Thank's for the info. I really appreciate that this is being addressed. Admittedly, I did rely on those emails. I will also try to work on the automated renewal and restart of all affected services.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [September 25, 2021, 2:12pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/10 "2021-09-25T14:12:55Z")

</div>

> [@Zulan](#):
>
> I will also try to work on the automated renewal

Let us know if you need any help along the way 🙂

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [September 25, 2021, 2:23pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/11 "2021-09-25T14:23:43Z")

</div>

Yeah, the [expiration emails](https://letsencrypt.org/docs/expiration-emails/) documentation seems to give the impression that it's something you can expect and rely on, whereas in my view the emails should be a last-ditch effort one would only see after several other things have gone wrong to let you know what your automated renewals and monitoring thereof didn't actually work.

---

<div class="post-metadata">

**Author:** ![jcjones](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jcjones/32/78_2.png) [@jcjones](https://community.letsencrypt.org/u/jcjones)\
**Post date:** [September 25, 2021, 4:19pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/12 "2021-09-25T16:19:26Z")

</div>

Good call. I've opened [Make the expiration emails page indicate that it's a best-effort service by jcjones · Pull Request #1304 · letsencrypt/website · GitHub](https://github.com/letsencrypt/website/pull/1304) which I won't claim is the right wording, but at least is a starting point.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [October 25, 2021, 4:20pm UTC](https://community.letsencrypt.org/t/missing-expiration-note-email/160457/13 "2021-10-25T16:20:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
