-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send mail via the systems mail subsystem #2793
Comments
I don't think this needs any work since it is already working (for me at least). I use exim4 on a Debian 12 as MTA. Hence all apps on the server can simply dump a mail() command to get stuff out.
Provided that your MTA actually works, i.e. test with something like:
you can setup Uptime Kuma alert with "SMTP" to your local MTA like so: and that's really all. To avoid confusion, maybe an entry could be added to say "Email (local)" without the unused fields from the SMTP setup to make this clearer. And/or in documentation. But the most important is that this actually works fine already so rest is nice2have/cosmetic and no showstopper. |
Adding another notification type just with fewer fields is not something that, I think would be beneficial. If you have ideas where helptexts/... would be benefitial, a Pull request would be appreciated That our monitor/notification system is something that we are aware of, but at least I currently don't have the spare time to document this more than currently done in the frontend. Related issue louislam/uptime-kuma-wiki#71 I am going to close this issue as reolved, thanks @apio-sys |
Thx a lot for pointing that out, @apio-sys |
Would be glad helping document SMTP sending via local MTA. But just to make sure before issuing a PR, would it be wanted as inline help text inside the monitor here: https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/smtp.js or in the help document here: https://github.com/louislam/uptime-kuma-wiki/blob/master/Notification-Methods.md ? Kind regards, Joris. |
Adding helptexts to notification providers requires editing two different locations. Foremost, text used in the The UI you see in the following screenshot is located here https://github.com/louislam/uptime-kuma/blob/master/src/components/notifications/SMTP.vue |
OK thanks for the clarifications. I need to setup a local dev env to test some stuff then. Would something like this:
help or not? In that case it won't be translated of course but I can't see where I could otherwise add help text. Maybe using a hover over a question mark (icon or not) and then get a help bubble that can then also be translated? Sorry for the noise, this is really not a big issue since it does work fine already but might help some people that wonder to work with local MTA vs remote SMTP (as I did myself when I started testing this great software a few months back). |
Great question, actually we currently have two ways of doing this:
I think for the usecase the second one fits better as likely a link to a piece of documentation/wikipedia what a MTA fits better
This is NOT noise. This is valid (encouraged!) discussion and has the upsides (among others) of f.ex.
|
OK thanks. Once this is decided I would be glad to contribute to the Wiki article that would be referenced. |
Once what is decided? When I was saying that linking to docs/Wikipedia might be a good idea, I was thinking about the Windows/macOS/Linux docs1 about sending mails or the Wikipedia article explaining what an MTA is. Footnotes
|
Well just to know we agree on to where to put that helptext and/or small wiki/doc. Either the simple way as per your point 1 and/or 2.a. or b. If we agree on where to put what, we can start working on it. |
Yes, helptext below the hostname field is fine by me |
🏷️ Feature Request Type
Other
🔖 Feature description
It would be great if UK would not only send mail via smtp but optional via the mail subsystem on the system it is installed at.
✔️ Solution
Make use of system MTA to send mail to receiver
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: