SMTP Notifications setup problem
See original GitHub issueDescribe your problem
Setup notifications with smtp not working with selfhosted mailcow mail-server.
I have the correct hostname, port and authentication settings because I tested it with a different software for mail notifications.
What I am curios about is, that in the logs it has connect ECONNREFUSED XXX.XXX.XXX.XXX:465 and not the actual hostname with domain. Maybe I understand SMTP or mail wrong but I thought it requires the use of the hostname for secure connections.
In the working version in the other software it won’t work with the ip address so I though maybe that’s the problem.
Info Uptime Kuma Version: latest Using Docker?: Yes Docker Version:20.10.9 OS: ubuntu-21-04
Issue Analytics
- State:
 - Created 2 years ago
 - Comments:13 (6 by maintainers)
 
Top Results From Across the Web
Email Notification Error - TechNet - Microsoft
I am trying to configure email notifications on my site server in order to get alerts emailed to me. My company is now...
Read more >Troubleshoot email notification problems—ArcGIS Monitor
If you're having issues with email notifications, consider the following: Check your email server settings and update them as necessary.
Read more >SMTP Connection Problems when delivering Email Notifications
When you receive this error, first check that the SMTP server is set correctly. If this is OK, then the most common causes...
Read more >Troubleshooting notification emails not being sent
If you have mail notifications enabled, M-Files server sends assignment notifications using assignment owner's email address by default. Some ...
Read more >Problems Configuring NSM SMTP Notifications
I'm running NSM 2.3.0-R9-8c0195ea and am having problems configuring system notifications via SMTP.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

In my opinion, iptables is not for human, I honestly cannot master it, even though I used CentOS 7 for many years.
Would suggest to turn off the firewall for a short time and test it again, which can make sure that the direction is correct first.
I think you can set a TCP monitor, see if Uptime Kuma can connect to your mail server first.