No firewall has been set yet. So is there any way to find what is the problem?
No firewall has been set yet. So is there any way to find what is the problem?
Ask your network administrator. 
Your test indicates outbound connections from your host system aren’t functioning. That’s outside the scope of Nextcloud itself. It’s an OS / host / network infrastructure matter.
You might see if you can make outbound connections to anything from your server (or if it’s more limited to your SMTP server).
Either way, we have no idea since it’s not something Nextcloud has any control over.
Also, keep in mind that since you didn’t fill out the support template we have even less idea about your server / hosting environment. 
1 Like
In addition to what @jtr said, you might also want to try to make telenet connections specifically to other mail services that offer smtps on port 465. If those connections time out as well, it’s likely that port 465 is blocked outbound, either on your Nextcloud server or somewhere else within the network infrastructure where your server is hosted.
However, if these connections are successful, it’s likely that Zoho is blocking your Nextcloud server, in which case you’ll need to contact them for a solution.
1 Like
A simple ping google.com should show, whether the server has an internet connection.
If not, check the network settings of the server (gateway address, DNS seems to work).
I tried using the ping command, which successfully establishes a connection to google.com, but the Telnet command does not receive any response when trying to connect to both Gmail and Zoho.
If a ping to google.com works, it means your server has internet connection, so far so good…
However, to rule out a specific issue with Zoho you need to test specifically other smtp servers over port 465, which is not going to work if you use telnet against the main domain google.com.
Also Zoho seems to block icmp packets, so a ping to smtppro.zoho.in is always going to time out, but telnet works when I test it from my computer.
Try the following:
telnet smtp.google.com 465
and
telnet mail.gmx.net 465
and
telnet smtp.fastmail.com 465
If the telnet commands above fail as well from your Nextcloud server, I guess outbound traffic to port 465 ist blocked either on your Nextcloud server directly or somwhere in the network infrastructure where your Nextcloud server is hosted.
If they work, you’ll need to contact Zoho, because then they are likely blocking the IP of your Nextcloud server.
1 Like
A third reason might be your router itself. If you use an AVM router for example in the guest network, all services are blocked by default, except Ping, http and https.
Please check the outgoing permissions of your Nextcloud in the router.
1 Like
Yes, it may well be a router/firewall/network configuartion issue. However to be able to help with that, we would need a lot more information.
I mean we don’t know anything, not even if the server is hosted at home or in the cloud with a VPS provider, which OS is used, how Nextcloud was installed etc…
I have tried all the Telnet commands in server, but they all fail. But from the local machine every command reflect with responses. I haven’t installed or configured a firewall yet, so there are possible issue might be related to my router blocking the connection. However, I’m using the same router for my home computer and mobile devices, and where those same connections are working fine with them.
FYI: I hosted my nextcloud with Akami (Linode).
Shortform:
1 Like
Many VPS providers do restrict email ports to prevent their VPSs being used to send spam, so that’s probably the case here too.
I would check their control panel to see if there are any firewall settings blocking outgoing port 465 that you can change yourself. If you can’t find any, or can’t change them, you’ll need to open a support ticket and ask them to do it for you.
I also found the following FAQ article. It’s five years old, so I’m not sure how relevant it is today: https://www.linode.com/community/questions/19082/i-just-created-my-first-linode-and-i-cant-send-emails-why-mailing-ports-25-465-a
1 Like
okay will check that too.
I don’t think so. Mail access wors from his workstation as written above, but not from his server only.
If blocked in the way you wrote above, access from my network via telnet might have been blocked. So i guess, that the block is somewhere between Nextcloud server and the router.
I guess so. How to troubleshoot and find where the fault?
Check the router log and its settings as well as the port-settins of the router where the server is connected to, if cable connection resp wireless settings of the wireless network, where the server is connected to.
Past recent threads suggest Linode blocks: See Nextcloud AIO Email Error - #6 by hblkr
But i don’t find any records within my Linode portal. Should i add one? If that yes, please say examples of records.
According to this post the server is hosted at Linode.
It’s not a DNS issue, it’s Linode blocking port 465 outgoing from their VPSs, and since you don’t have any issues sending emails from your computer, I don’t think you need to change any DNS records for your email domain.
You could try to use an external mail proxy/relay service like fastmail, as the user did in the other thread, but that makes things more complicated.
So I would first try opening a support ticket with Akamai/Linode explaining why you need to send email from your server and asking them to open port 465. If they follow through with your request, I’m pretty sure it will just start working.
and here: https://techdocs.akamai.com/cloud-computing/docs/send-email#request-to-lift-restrictions
1 Like
Hello everyone,
I successfully configured my email after reaching out to Linode due to some restrictions. I wanted to ask whether I should continue using my existing email, or if it’s possible to create and use a dummy email, such as “nextcloud@zogo.com,” even if it doesn’t actually exist.
I have a few more questions to ask—should I open a new ticket for those, or can I ask them here?
Thanks!
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.