Objective: Need to install an SMTP server (preferably postfix) that will send messages to other common mail providers like gmail, outlook, yahoo, etc.

Problem: Google Cloud blocks usage of SMTP port 25 (but not 465 or 587) and only provides details on how to use external mail providers. Another workaround is to create a gmail account, configure relay as smtp.gmail.com and use the said account to send the messages. The problem with this is that the daily message limit for the relay is probably going to be exceeded with the volume of messages that are expected to be sent.


  1. Sending a message using mail on ubuntu 18.04 on google cloud using the default postfix configuration and only changing "inet_protocols" to "ipv4". This gives a timeout message on log.

postfix/smtp[]: connect to ALT2.ASPMX.L.GOOGLE.COM[x.x.x.x]:25: Connection timed out

  1. Tried changing the following lines in master.cf

smtp inet - - y - - smtpd

smtp unix - - y - - smtp


587 inet - - y - - smtpd

587 unix - - y - - smtp

adding "smtp_use_tls = yes" to main.cf

and restarting postfix. This puts postfix listening and sending messages on port 587, but it still gives the same massage.

postfix/smtp[]: connect to ALT3.ASPMX.L.GOOGLE.COM[x.x.x.x]:587: Connection timed out

  1. Messages are sent by using the same configuration as on 1 in another hosting service (port 25 not blocked).

There are people that say smtp between servers only works on port 25, but I've been unable to find any information that confirms this, and not knowing much about mail servers am unsure if it's at all possible to configure another port on postfix for this effect.

Am I just wasting my time trying to configure this on Google Cloud and should just change hosting service? Or is there some kind of way to configure postfix to work with port 25 blocked?

  • Indeed all mailservers expect incoming mail to arrive on port 25 , the designated port for smtp. Standards for improved SMTP were developed that use other ports but those never really took off, making port 25 the universal standard for email. (The other ports are commonly used only by authenticated users of that mail domain and not for incoming messages from other mail servers ) Since Google blocks port 25 you need a relay service that accepts your outgoing email on a port that is not 25 and will forward your mail to its destination
    – Bob
    Nov 23, 2020 at 11:10
  • I guess I there's no way around it then. Thanks for the help.
    – js1018
    Nov 23, 2020 at 11:59

1 Answer 1


This was first decided back in 1982 with RFC 821, Appendix A and has been this way ever since. Currently the TCP port 25 is IANA assigned for this purpose, too. From SMTP RFC 5321: Receiving Strategy

The SMTP server SHOULD attempt to keep a pending listen on the SMTP port (specified by IANA as port 25) at all times. This requires the support of multiple incoming TCP connections for SMTP.

You cannot simply change the port, because there is no mechanism for other SMTP servers to know you are using a non-standard port, and you cannot either send to other servers using any other port.

The Google Cloud is not designed for this, as explained in their guide: Sending email from an instance:

Using standard email ports

By default, Compute Engine allows outbound connections on all ports except port 25, which is blocked because of the risk of abuse. All other ports are open, including ports 587 and 465.

Note: Port 25 is always blocked and can't be used, even through an SMTP relay using Google Workspace.

The ports 587 and 465 are available for SMTP Message Submission (RFC 6409). This means you can use an external mail relay (your own or from someone else) for authenticated SMTP, and this server handles delivery to other mail systems on port 25.

  • I see. I guess I can only change hosting provider since my company doesn't want to incur the cost of using an external provider. Thanks for the detailed explanation.
    – js1018
    Nov 23, 2020 at 11:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .