E-Mail Subscription by Status-Page #2073

Closed
opened 2026-02-28 02:42:08 -05:00 by deekerman · 2 comments
Owner

Originally created by @pavl21 on GitHub (Apr 4, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

New Notification, Other

🔖 Feature description

Provide an option on the status page to send an e-mail when the status changes. As well as a message to all subscribers when there is maintenance work.

✔️ Solution

E-Mail Subscription via Status-Page and SMTP-Configuration

Alternatives

No response

📝 Additional Context

No response

Originally created by @pavl21 on GitHub (Apr 4, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Notification, Other ### 🔖 Feature description Provide an option on the status page to send an e-mail when the status changes. As well as a message to all subscribers when there is maintenance work. ### ✔️ Solution E-Mail Subscription via Status-Page and SMTP-Configuration ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

@CommanderStorm commented on GitHub (Jun 12, 2023):

@pavl21 is this a duplicate of https://github.com/louislam/uptime-kuma/issues/916?
If no, could you make this issue more distinct?
If yes, could you close this issue? (duplciates only hurt the project)

@CommanderStorm commented on GitHub (Jun 12, 2023): @pavl21 is this a duplicate of https://github.com/louislam/uptime-kuma/issues/916? If no, could you make this issue more distinct? If yes, could you close this issue? (duplciates only hurt the project)
Author
Owner

@CommanderStorm commented on GitHub (Dec 3, 2023):

@pavl21
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #916 as there is no functional difference and the other isuse has more support and a deeper discussion
⇒ I am going to close this as a duplicate

@CommanderStorm commented on GitHub (Dec 3, 2023): @pavl21 We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #916 as there is no functional difference and the other isuse has more support and a deeper discussion ⇒ I am going to close this as a duplicate
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2073
No description provided.