Unfortunately, the error message remains the same.
Is it possible for you to try personal Gmail credentials so that we can try to filter the cause of the problem? As in, is it because Google Workspace SMTP is not allowing connections from Netlify, or anything of that sort. Additionally, if you could try a random third-party SMTP that doesn’t rely on Google, that could also help us narrow down the problem even more.
Thanks, Hrishikesh.
What you suggest is what I previously configured, which as of early yesterday (my time) didn’t work for your tests. Let’s call this Config1 since it is what Netlify recommends.
Then late yesterday I tried configuring with a different approach recommended by Google when your documented approach fails. We can call that Config2. That is what you also reported as failing in your most recent email that I am here replying to.
I have consistently used Config1 throughout the tests, except for the most recent attempt to use Config2. Unfortunately both have failed.
I must say that the documentation on both sides of this is quite murky. It’s like we need to put a Google Workspace Email engineer and a Netlify integration engineer together, not just to solve the problem, but also to explain what they did so that someone can commit the potion to writing.
I wonder why this is not already turnkey. I did find another Netlify Support forum post from a few months ago where someone else was trying to do the same thing and experiencing exactly the same problems. To my disappointment the post is inconclusive as to whether the other user was ever successful, and if so, how. Dennis, one of your Support Engineers, seems to have had the most knowledge:
https://answers.netlify.com/t/custom-sender-address-error-recovering-user/34032
The below discussions are not our use case, but might be related:
https://medium.com/@jacobsowles/how-to-deploy-a-google-domains-site-to-netlify-c62793d8c95e
In other words, we are not hosting our production Netlify app domain on Google, and our test sites of course don’t host on Google. Our set up is as follows:
If we can’t get our parent company email to work, perhaps we should not use the parent company domain email account, but use the app domain as the email account on a different email host. This seems to be better supported and works for others:
https://answers.netlify.com/t/support-guide-how-can-i-receive-emails-on-my-domain/178
That would be our last alternative as I’d sure prefer to get the parent company emails to work.
We’re trying to figure this out with you, and hopefully after we resolve this, we can work on what parts of documentation to improve.
From what I know, custom SMTP is currently working fine for a lot of users and this error text dial tcp 64.233.181.27:587: i/o timeout is not particularly helpful. It’s just saying that the connection to Google timed out.
This is why I said, try using a different SMTP provider temporarily - just to isolate the source of the problem. At the moment, we’re trying to guess the source of the problem - it could be Google, it could be us. Now we know the functionality is working for other websites, but I suppose the same SMTP credentials would be working for you elsewhere too. So, we’re back to the same question as to where the fault exists at the moment. This can only be solved by taking out one variable at a time and in this case that would be a different SMTP host.
If that works, you would also get some concrete information that might help in getting help regarding this from Google. If not, we can file a bug for our engineers to investigate.