Or … the real reason that this is an issue MOST ALWAYS is because the provider has blocked outbound connections to port 25. Not because the inbound server is blocking them … the outbound server will not allow connections to be made OUTBOUND on port 25.
Hence, my suggestion for the OP to ticket his provider again to confirm that they actually DID unblock port 25 capabilities.
I can easily verify this as my home ISP blocks such requests, as does another hosting ISP that I have recently started using but am not currently concerned with correcting the issue.
However, from any of my Vultr instances I get the following output from telnet:
$ telnet box.occams.info 25
Trying 94.76.202.152...
Connected to box.occams.info.
Escape character is '^]'.
220 box.occams.info ESMTP Hi, I'm a Mail-in-a-Box (Ubuntu/Postfix; see https://mailinabox.email/)
So telnet can be used to test if this is being blocked, and the posts above indicate this is not the case for their MiaB hosting provider.
The status checks failure for port 25 means that the box is unable to connect to aspmx.l.google.com. If you somehow are able to connect to other servers, this may indicate Gmail is specifically blocking connections from you or your ISP (but it could be something else, too).
Okay, so I wrote a ticket to my provider telling him about the issue. They tried giving me a new IP Address and checked again on the blocking of port 25. Somehow everything is fine now and I really don’t know why. I’m not complaining just confused. Maybe they didn’t really unblock it.