SMTP error with smtp.mail.yahoo.com, but I don't use this?
-
Hi, I started getting this error recently. I looked in the logs for the domain/app in question but nothing with 'yahoo' appears. And the email setup for this domain is Outbound only, using the Built-in SMTP Server. How can I see what is causing this error?
Relay error: Connect to smtp.mail.yahoo.com timed out. Check if port 25 (outbound) is blocked Email Status is checked every 30 minutes. See the troubleshooting docs for more information.
-
This is actually just a email status checker which in this case wants to verify that port 25 is open for outbound connections. Most server providers block port 25 by default and we want to show that in the UI.
The whole list of servers the Cloudron tries to reach is at https://git.cloudron.io/cloudron/box/-/blob/master/src/mail.js#L102
Maybe we should consider not checking that often though. The status of the outbound firewall usually does not change frequently.
-
@scooke You can check if
telnet smtp.mail.yahoo.com 25
works on your server. If it doesn't i means that outbound mail is blocked from your server. You have to contact your VPS provider to unblock outbound port 25.If you are aware of this and don't care about sending out emails, then you can go to Email -> Select domain -> Outbound -> Disabled. That will remove the above notification.
-
@girish But, I want Outbound enabled. And under this option, it says I'm using the Built-in SMTP Server. So, does Cloudron use yahoo? When I click the Send Test Email icon an test email is successfully sent and received. And in the Raw Headers of the received email there is nothing about yahoo (just my Cloudron domain). So, did you mean in an earlier statement that Cloudron tests outgoing smtp servers? As in, a bunch of them? Why would it check the yahoo smtp server? (EDIT: I just checked https://git.cloudron.io/cloudron/box/-/blob/master/src/mail.js#L102 and it looks like the yahoo smtp check was removed. This makes sense since the Yahoo smtp server isn't a default option in the Outbound settings, although it looks like someone could use it if they set it up manually.) And since that edit was 3 hours ago I haven't yet received another notice about this, so I guess it has been taken care of. Thank you!
-
@rmdes I don't think the rate limit is less than once every 30 minutes ^^
However, the check could indeed be done at intervals depending on the situation. Like do the check immediately when the config is changed, do it every 30 minutes or so until it succeeds once, then only once every day, and try 3 times before printing a warning (it could just be a random network timeout)
-
I just started getting this error too: