How can we improve Compute Engine?

Send and receive email using TCP SMTP IMAP ports

Our software is also an online email client for all our customers, we cant use Google Cloud engine if we have tcp smtp ports closed!

We need to send email using port 465 and 587

833 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
completed  ·  AdminScott Van Woudenberg (Admin, Google) responded  · 

Hello again everyone,

Following up on Paul Nash’s recent update, we (the entire Compute Engine PM team) are very happy to say that this change is now in production. In other words, Compute Engine customers can now connect to external SMTP servers and services using ports 465 and 587.

We appreciate all of the votes and feedback our community has provided around this issue. If you encounter issues with this functionality, please submit bug reports using our external issue tracker1.

135 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • AdminPaul Nash (Product Manager, GCE, Google) commented  ·   ·  Flag as inappropriate

    REMINDER: This item is now closed. Ports 465 and 587 are enabled outbound for all projects. Port 25 is being tracked on a separate feature request. We cannot provide 1:1 technical support in this forum, so please utilize other avenues like gce-discussion or contacting Cloud Support if you need help with an individual issue.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Hi
    Google VM Instance SMTP port 25, 465,587 not working can anyone help me how to enable the port i have already set firewall roles but still not woking

  • Suresh Kumar commented  ·   ·  Flag as inappropriate

    Please open up the SMTP ports ASAP. It is not justified to force clients to use any third party mailing solutions

  • Rainer Alföldi commented  ·   ·  Flag as inappropriate

    Why is this issues closed and voting for it no longer possible?! Are port 465 and 587 supposed to be a solution?! Really?

  • Lorant Nemeth commented  ·   ·  Flag as inappropriate

    After convincing the customer to move their workloads to GKE and having one of their applications (does not need port 25) running in production @google ready, now we'll move all applications back to Amazon (they don't want to have two cloud service providers for their two applications) only because of this limitation (they are required to used their customers SMTP servers, which many still use port 25).

    Before we start moving back things, can you confirm, that there's not even a manual process in order to enable port 25?

  • Emrah commented  ·   ·  Flag as inappropriate

    Please open up the SMTP ports ASAP. It is not justified to force clients to use any third party mailing solutions

  • PCS Web commented  ·   ·  Flag as inappropriate

    It turns out 587 and 465 are for secure clients connecting to your email server — a necessity for sure. Emails come from your clients to your server where they are then sent off to their destination servers across the internet. So, to successfully send email out of your own server to other destinations we also need port 25 opened for SMTP inter-server communication between the origin server and the destination server. So this still is NOT a complete working email server scenario for most people, including me. Sendgrid or another external SMTP server, or even a MS Exchange server or Outlook service must still be used despite Google opening these two ports.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Just to make things clear, so with that being said, we can use 465 and 587 to send outgoing mail with postfix as smtp. Currently having problem sending outgoing to gmail accounts.

  • Anonymous commented  ·   ·  Flag as inappropriate

    je veux configurer mon propre serveur mail, je peux rien faire si le port 25 est bloqué !!!!!!

  • PCS Web commented  ·   ·  Flag as inappropriate

    I run this script:

    ###########################

    #!/bin/bash

    date "+------- GCE PORT OPENING CHECK ----------- %Y-%m-%d %H:%M:%S -------"
    outgoing25=$(curl -vsS --insecure --connect-timeout 2 --ssl https://smtp.gmail.com:25/ 2>&1 | grep Connected | wc -l | awk '{$1=$1};1')
    outgoing587=$(curl -vsS --insecure --connect-timeout 2 --ssl https://smtp.gmail.com:587/ 2>&1 | grep Connected | wc -l | awk '{$1=$1};1')
    outgoing465=$(curl -vsS --insecure --connect-timeout 2 https://smtp.gmail.com:465/ 2>&1 | grep Connected | wc -l | awk '{$1=$1};1')
    if [ $outgoing25 == 1 ]; then echo "Port 25 is OPEN"; else echo "Port 25 is CLOSED"; fi
    if [ $outgoing587 == 1 ]; then echo "Port 587 is OPEN"; else echo "Port 587 is CLOSED"; fi
    if [ $outgoing465 == 1 ]; then echo "Port 465 is OPEN"; else echo "Port 465 is CLOSED"; fi

    exit
    #################################

  • Andre commented  ·   ·  Flag as inappropriate

    Hi. Anybody know a way to test if the ports are open. I think mine are still closed

  • Derese Getachew commented  ·   ·  Flag as inappropriate

    Is this Working for any one ? i am Allowed TCP 465 on my firewall to connect to GoDaddy it works from my servers but fails from my GCloud instance ?

← Previous 1 3 4 5 6 7

Feedback and Knowledge Base