Notifications don't work - routing/network config related?
I want to use the system notifications configured under System / Advanced / Notifications and have entered both SMTP and Telegram settings. Neither of the services are able to connect.
The settings are definitely correct, and the SMTP server is entered correctly. I am using the exact same settings and accounts for other devices on the network successfully.
Upon connecting with "Test SMTP Settings", I receive the error message: "Could not send the message to *****@gmail.com -- Error: Failed to connect to ****:25 [SMTP: Failed to connect socket: Operation timed out (code: -1, response: )]"
If I test the SMTP server host under diagnostics -> test port and enter the SMTP server, it also fails: Connection failed.
The same happens if I use the IP address instead of the URL, so it is not DNS related.
I figure it must be routing / network related that the notification services running as localhost cannot reach out to the SMTP server. I have however got a localhost to WAN NAT rule, and it is e.g. possible without problems to download and upload the firmware from within the pfsense admin GUI.
Do you have any hints where else I could troubleshoot or review logs to tackle this? I would really love to have the notifications up and running. Thanks for any advice.
Gmail doesn't accept SMTP connections on port 25. Use port 587 instead.
@viragomann I'm sending via my own SMTP, gmail is just the recipient address, so unfortunately it needs to be something else :-(
Anyway, pfSense is obviously not able to access the SMTP server.
So how is you SMTP server connected? Is it inside your LAN or in the internet?
What are your outbound NAT rules?
Some floating firewall rules defined?
Gertjan last edited by
I'm sending via my own SMTP
Error: Failed to connect to ****:25 [SMTP: Failed to connect socket:
port 25 is meant to be used to receive mails from the 'outside world' == only other mail servers use this port, to drop mails that are destinated for you - you MX domains..
A mail client, like Outlook 365, Thunderbird or pfSense in this case, should use 587 or even 465.
You should set up your own postfix ? mail server to accept mails from YOUR clients on these ports. And set up all your clients to use only 587 or (better) 465.
True, in the last century, mail client could use port 25 of the mail server of your ISP. That was wrong.
Btw : most ISPs completely block outgoing connections to anywhere:25 these days (except there own mail server).
@gertjan Thank you! It works now ... Should've known that, won't make that mistake again!