Why Google Compute Engine doesn't accept port 587?

[Saraag in]

Why on earth Google Compute Engine doesn't accept port 587 to send email? Our company already purchased email with third party. But now we came to know that bloody Google doesn't accept port 587. Why the hell we need to pay separate amount for this?

[Steven Osborne]

They've got some documentation regarding sending mail from an instance: https://cloud.google.com/compute/docs/tutorials/sending-mail/

I encountered a similar issue not too long ago, one of my clients uses Zoho for their team's email service and was having trouble authenticating and sending mail from an instance using Zoho. The solution for me was Mailjet. Using them as a relay, the instance is able to authenticate and send mail.

Hope this helps.

[Paul Nash]

(re-posting public, accidentally replied directly)

Sorry, but we currently do not allow this due to the reasons listed here [1], and this has been documented in this group before as well. Even well-intentioned users pose attractive targets for attackers who would like to use Google IPs for disreputable activities.

I don't know what service you might mean by a "third party" in this case, but you may be able to access their API through an http style gateway vs. smtp on ports 25, 465, or 587.

[1] https://cloud.google.com/compute/docs/tutorials/sending-mail/

PS - Google believes in a diverse, civil, and respectful community. We would appreciate it if you could please choose polite language in accordance with these principles. We want everyone to feel welcome here.

Thanks

On Sat, Mar 11, 2017 at 4:29 AM, Saraag in <saraa...@gmail.com> wrote:

Why on earth Google Compute Engine doesn't accept port 587 to send email? Our company already purchased email with third party. But now we came to know that bloody Google doesn't accept port 587. Why the hell we need to pay separate amount for this?

--
© 2017 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/656983ef-04b7-4575-8bfb-a99230e35004%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Paul R. Nash |

Product Manager, Compute Engine |

paul...@google.com |

206-876-1620

[Fedon Kadifeli]

Although it is documented, I am not satisfied with the rationale behind this decision to block these ports. Your major rival (AWS) does not have this restriction and AFAIK nothing bad happens. On the other hand, I think every instance should be able to send e-mails (at least to their instance owners) for alerts. How am I supposed to receive e-mails sent to user root by Linux OS or utilities running in my VM instance without logging in to my instance and manually checking root's e-mails?

[Paul Nash]

Thanks for your feedback. We definitely understand your concerns, but don't have any changes to announce at this time. It turns out this particular request is not currently tracked on our UserVoice forum, which is one tool we use to gauge the amount of customer interest in future feature requests. If you'd like to file an item there so you can get notifications of any changes, we'd love to have it there for others to vote on too (I'd file it, but I can't sign up as you! :) ).

https://googlecloudplatform.uservoice.com/forums/302595-compute-engine