I somehow nuked my test site. The fact I'm not sure how or why it happened is very troubling. I guess I'll have to be way more careful with Plone than I was with Wordpress which has survived 2 years of noobie admin abuse (and countless marginal plugins).
Anyway, I will start again and get back to you with the event.log entries.
By the way, is there any difference in using the Plone app installer (Bitnami) on Google Cloud vs installing it from CLI (like I did on Digitalocean)? Are both installations "correct/supported"?
[quote="tkimnguyen, post:8, topic:3370"]
Yeah it's your firewall.
[/quote]Thanks for clarifying. I will deal with this later since it's not important for my test site and also because I'll likely be hosting my production site elsewhere.
I just wanted to update this just in case someone else came across the same issue. Anyway, from the Google Cloud website:
Using standard email ports
Google Compute Engine does not allow outbound connections on ports 25, 465, and 587. By default, these outbound SMTP ports are blocked because of the large amount of abuse these ports are susceptible to. In addition, having a trusted third-party provider such as SendGrid, Mailgun, or Mailjet relieves Compute Engine and you from maintaining IP reputation with your receivers.
So the problem is that you can't use outgoing ports of smtp. Thanks Google. Now like a good customer I sat and thought. How can I bypass that and do what they don't really want me to do.
So the solution I found was setting up a Microsoft Flow to receive POST request over https andfrom that request to send an email.
I also added a simple auth to make sure no one sniffed my url and started using it himself. So I added a condition to make sure the field key in the post's body was equal to what I defined.
That was the request going from Google in on port 443. Problem solved. Now no reputation to Google's IP is affected.