Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

SMTP port

Hi guys.

WIth my previous company (google cloud customer) we have smtp port 25 opened for sending.

Now i've changed the company and opened a new google cloud account but the port 25 is blocked.

can I do something or ask to someone to get this limit removed ? As we had some mailserver on the previous google cloud account that need to be moved under the new account (and a brand new mail server to spin up) but with the port closed I can't do this.

On AWS I was able to wave the limit simply by asking to AWS support

2 4 699
4 REPLIES 4

Hello @LauraM  ,Welcome on Google Cloud Community.

Well, you could:

1. Use 3rd party solution for SMTP stuff like Mailgun or SendGrid. 

2. Consider Using Different Ports: If you'd rather not use an external email service, you can attempt to adjust your email server to operate on a different SMTP port, like 587 or 465. These ports are usually not restricted by default on GCP. Keep in mind that this approach may have its drawbacks and may not be the best choice.

--
cheers,
DamianS
LinkedIn medium.com Cloudskillsboost

It's a primary smtp server, I can't use different ports because smtp-to-smtp ports it 25/tcp.

587 is for submission (MUA to smtp server) and that's not the case.

Also, with my old company the smtp port was open and used with no issue at all for years, why isn't the same for the new company ?

25 has been disabled due to security reason. If you had 25 enabled, most probably it has been configured, based on TAM (https://cloud.google.com/tam?hl=en) request (" However, this traffic is not blocked in projects owned by select Google Cloud customers." / https://cloud.google.com/firewall/docs/firewalls#blockedtraffic). So if you have Technical Account Manager on place, you should be able to enable 25 SMTP for particular project. 

PS: "Even though you explicitly configure a firewall on port 25 for your, it will be blocked by the Google SMTP constraint policy" / Source topic: https://www.googlecloudcommunity.com/gc/Infrastructure-Compute-Storage/Enabling-Port-25-for-My-Proje...

 

With the previous company, we didn't have a TAM, it was opened.....

Much easier to move to other cloud, with less stupid restriction, like AWS. Just ask  (did multilple times) and they will open the port. If you are able to manage the security for your cloud, there is no need to block legit customers. You have to block legit traffic only if you are unable to manage the security in a proper way, much easier to block everything to everyone than fix the issue.