Add a note about using Gmail vs an Email catcher #17586
Conversation
I prefer not to. This is really a foot gun as the configuration for Gmail is really hard and there are so many alternative out there that are better. I could even suggest deprecating support and removing it in 7.0. |
|
Other services usually require domain verification, which is not always possible in an early phase of a project, but deploying a test site to get early feedback is mandatory. I use Gmail and Google Groups (as a catch all address) in this case to handle sending emails, and it works great. Please do not remove Gmail, without a free and usable alternative which works without domian verification. I can update the docs if needed. |
|
@1ed Here, we are only warning users. I suggested that we could even deprecate support, but we won't :) |
|
@1ed But we are looking for someone who can update the docs to explain exactly how to configure it as many people struggle. |
|
@1ed a while ago I suggested some rewords for Gmail article after having to use it in my own projects. I wonder if they are still correct: https://github.com/symfony/symfony-docs/pull/5856/files |
I can do that. @javiereguiluz I will check the current docs and maybe write step-by-step instructions. I'm quite busy atm, but give me some time to come up with something. These changes look great by the way, I just wanted to share my use case. |
|
I've merged this because it's a nice improvement in the existing docs. Thanks Fabien. But, @1ed if you can find some time in the future to improve the situation around Smyfony Mailer + Gmail, please try to create a PR. Thanks! |
…(1ed) This PR was merged into the 5.4 branch. Discussion ---------- [Mailer] Add a note about how to use the Gmail provider Based on #17586 (comment) Commits ------- 1a25297 [Mailer] Add a note about how to use the Gmail provider
We have many people complaining about the difficulty to set up Gmail. But we should recommend not using it as this is not a good way to send emails from an application. I've also added a note about using an email catcher as I think this is the way to go in development (and automatically configured nowadays via our Docker integration).