mirror of
https://github.com/acme-dns/acme-dns.git
synced 2026-04-27 04:45:48 +03:00
[PR #227] [MERGED] Add support for LE expiration notification e-mails on API cert #351
Labels
No labels
Documentation
Documentation
bug
enhancement
feature request
feature request
help wanted
pull-request
question
security
security
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/acme-dns#351
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/acme-dns/acme-dns/pull/227
Author: @blkeller
Created: 4/29/2020
Status: ✅ Merged
Merged: 1/11/2021
Merged by: @joohoi
Base:
master← Head:notification-email📝 Commits (1)
f89224aAdd support for LE expiration notification e-mails on API cert📊 Changes
4 files changed (+6 additions, -0 deletions)
View changed files
📝
README.md(+2 -0)📝
config.cfg(+2 -0)📝
main.go(+1 -0)📝
types.go(+1 -0)📄 Description
Summary:
This PR adds support for setting an e-mail address in the config file that Let's Encrypt can use to send notification e-mails if the API's certificate is expiring soon. When an account at LE is registered and an e-mail address is provided, LE will use this address for this purpose:
https://letsencrypt.org/docs/expiration-emails/
This is a helpful, optional service that LE offers for free, and the e-mails can be useful for an admin to be alerted to potential certificate renewal issues that might otherwise go unnoticed.
The new config option
notification_emailis an empty string by default, preserving the previous behavior of not registering any address with LE upon account creation. If the user fills in an e-mail address, this value will be used during account creation with LE.The value of
notification_emailis passed through to CertMagic and leverages their existing support for this feature.Example:
Where the config file includes these entries:
This patch yields the following results:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.