If you were at home, sending email, maybe the test is not valid. Port 25 is not blocked on your Yunohost, and not on your LAN. If you tested it with your laptop on the home network, there is no problem with port 25.
If I got it straight, port 25 needs to be open on your server to receive incoming connections from other servers.
I guess you got another mail account somewhere. If you sent an email from that account to your Yunohost-account, does it arrive?
Another thing to do for sure, is using https://www.mail-tester.com/ which gives a nice overview of everything that is correctly configured by Yunohost (I recall only a warning about missing an ‘unsubscribe’ link, which I can live with for my personal emails )
After all this, it could be a false positive. For a long while I had a warning in the diagnostics that port 25 was open, but that another program seemed to be listening. I never found out why that happened.
Hardware: Root Server by Netcup YunoHost version: 4.3.6.2 (stable) I have access to my server : Through SSH | through the Webmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Starting Nmap 7.70 ( https://nmap.org ) at 2022-03-12 11:50 CET
Nmap scan report for smtp.gmail.com (64.233.167.108)
Host is up (0.011s latency).
Other addresses for smtp.gmail.com (not scanned): 2a00:1450:4013:c08::6c
rDNS record for 64.233.167.108: wl-in-f108.1e100.net
PORT STATE SERVICE 25/tcp open smtp
Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds
Hello,
Same here also. I use a VPN (Aquilenet, an FFDN member) and my ISP is Bouygues. I can send mails to other servers without any problem. So definitely, it seems to be nothing more than a false positive.
Same here. Nothing change and since 2 days the diagnostics show me the port 25 is blocked but all (ISP, router, firewall are unchanged and they seem OK).
My ISP IS free and I use a VPN FDN on my router.
I can send mails to other servers without any problem too. So it seems too a false positive
The problem seems to be related to the way the diagnosis works - it connects to yunohost.org on port 25, but a test just now shows this port is refusing connections (not just blocked - this would give a timeout):
sudo /bin/nc -4 -z -w2 -v yunohost.org 25
nc: connect to yunohost.org port 25 (tcp) failed: Connection refused
Is there a change to the setup of the yunohost.org server on port 25?
This may have been a false positive related to our DNS server being down. This has been fixed. Let us know if tonight’s diagnosis still shows the error.