I'm able to receive email, But Can't Send it

SYSTEM INFORMATION
OS type and version Operating System: Rocky Linux 9.4 (Blue Onyx)
Virtualmin version Virtualmin version v7.20.1

I went to “webmin Servers\Postfix Mail Server Mail Queue”
I have 5 mails on the queue …
connect to alt2.gmail-smtp-in.l.google.com[2607:f8b0:400c:c08::1b]:25: Network is unreachable
connect to alt2.gmail-smtp-in.l.google.com[108.177.12.26]:25: Connection timed out
connect to alt2.gmail-smtp-in.l.google.com[2607:f8b0:400c:c08::1a]:25: Network is unreachable
connect to alt2.gmail-smtp-in.l.google.com[2607:f8b0:400c:c08::1a]:25: Network is unreachable
connect to alt2.gmail-smtp-in.l.google.com[108.177.12.26]:25: Connection timed out
I’m using Cloudflare for my DNS
I already created SPF, .Domainkey, and DMARC records exactly the same as my virtualmin server, I use DS Record from cloudflare and added to my DS records in my domain registar …
What am I doing wrong ???
Thanks

your port 25 is blocked for outgoing mail. get your provider to unblock it.

Port 25 is not been blocked …
Title Port |Result|
| — | — | — |
|Custom Port # 1| 25 |Open|
|Custom Port # 2| 465 |Open|
|Custom Port # 3| 587 |Open|
|Custom Port # 4| 993 |Open|

Results are from:

This tool can only check the inbound connection. If your provider blocks port 25, that is outgoing.

Can you provide any other reasonable explanation as to why the network would be unreachable? Try pinging from the server.

mit@~:ping alt2.gmail-smtp-in.l.google.com
PING alt2.gmail-smtp-in.l.google.com (173.194.219.26) 56(84) bytes of data.
64 bytes from ya-in-f26.1e100.net (173.194.219.26): icmp_seq=1 ttl=53 time=42.2 ms
64 bytes from ya-in-f26.1e100.net (173.194.219.26): icmp_seq=2 ttl=53 time=40.1 ms
1 Like

PING alt2.gmail-smtp-in.l.google.com (108.177.12.27) 56(84) bytes of data.
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=1 ttl=99 time=31.7 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=2 ttl=99 time=36.5 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=3 ttl=99 time=31.4 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=4 ttl=99 time=31.7 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=5 ttl=99 time=33.4 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=6 ttl=99 time=31.8 ms
64 bytes from ua-in-f27.1e100.net (108.177.12.27): icmp_seq=7 ttl=99 time=32.2 ms

So if the network is reachable via impc protocol, then why isn’t it with TCP? I’d say your provider is blocking outbound port 25 just as @shouders suggested.

if i do telnet my mail.server.com 25 i’m able to connect to my server … meaning port 25 is open right ?
Thanks

You seem to be confused about inbound vs outbound. Networking 101. A path to something doesn’t ensure a path back.

Check with your provider. If you want to share who it is with us someone may have experience. Amazon? Not gonna happen.

probably, the only option left for me could be setup another server in a different network, open port 25, and see if i can reach it from this network…

Thanks for your input

You keep checking inbound. That’s not what anyone is saying is blocked.

Try telnet on port 25 from your server to some mail server, like Google. That tests outbound, and I’m confident, based on the logs above, it will time out.

I already did,
traceroute
telenet

and all of them failed !!! but at the same time I checked port 25 on alt2.gmail-smtp-in.l.google.com, timeout on me from the port checker …
port checker is checking INBOUND port 25 connection to alt2.gmail-smtp-in.l.google.com and is just timeout …
So, ii’s kind of difficult to said my port 25 outblund is blocked if that google server address on port 25 is not responding …
that is my point …

@Joe just told you how to check:

This is a VERY COMMON PROBLEM. It is a spam prevention method. Providers don’t want to have their networks blocked over spam.

Many providers will unblock port 25 if requested, and if you don’t use it to send spam.

The alternative is using a mail relay service like Mailgun, Sendgrid, Amazon SES, etc. Many have a free tier that would be sufficient for very light usage, and SES would only cost a few cents a month if you’re just using it for normal mail, and not bulk mail. We pay about 10 bucks a month for all of our mail relaying, which (I use it for some of our notifications since maintaining deliverability for things like forum notifications is hard, because people don’t bother to unsubscribe and start marking it as spam when they don’t want it anymore or forget they signed up for it, despite having subscribed to receive it). I think we send about 10-20 thousand emails a month. We still host our regular email ourselves, though, but we’ve been on the same IP for many years and our provider doesn’t block port 25.

I’ll also note this has been discussed a couple of times a week for a decade or so. You won’t have trouble finding many discussions about this problem.

But, it’s not a problem you can solve with configuration…your hosting provider either needs to open the port, or you need to relay through some server that has port 25 available. You can’t send mail without port 25 (and I’ll add, preemptively, since this conversation often goes there at some point, you also can’t make the rest of the world accept mail on any other port…you either have port 25 or you can’t send mail directly from your server to other servers on the internet).

Joe,
Thank you for your comments!!!
I contacted my ISP Provider, and they were able to open port 25 outbound !!!
Mail is working sweet !!!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.