Using Google SMTP with Supabase Custom SMTP #19646
Replies: 6 comments 7 replies
-
Very much appreciated these instructions. I had been using Google's SMTP service since January based on them. I wanted to let people know about an error that I had starting a couple days ago. My signup functionality stopped working and it was only obvious in supabase logs. After troubleshooting for several hours, I narrowed it down to a SMTP auth error. When I swapped SMTP providers everything worked fine (after many other failed attempts to solve the issue). No idea why my account for Google just stopped working, but if anyone encounters this error, hopefully it'll save you time. |
Beta Was this translation helpful? Give feedback.
-
can i use my free gmail account? |
Beta Was this translation helpful? Give feedback.
-
Very useful tutorial. Thank you very much, it works perfectly for my project. |
Beta Was this translation helpful? Give feedback.
-
Thanks to this guide, I was able to set it up successfully in 2024.
|
Beta Was this translation helpful? Give feedback.
-
it works, but the email template even tho i changed it, it is not applied |
Beta Was this translation helpful? Give feedback.
-
Quick question: Why am I required to add a custom SMTP to supabase when I don't use Supabase email verification? |
Beta Was this translation helpful? Give feedback.
-
Hey everyone, i've been hearing feedback about how challenging it can be to get google SMTP working properly with Supabase. I've tried setting this up with a trial google workspace account and this is what i've discovered.
smtp-relay.gmail.com
only port 465 works. If you want to usesmtp.gmail.com
, you can use port 465 or 587 (both ports worked for me).I'm also gonna include some screenshots below on what those steps look like:
For
smtp-relay.gmail.com
(The "Require TLS encryption" option doesn't seem to affect anything during my testing)
For
smtp.gmail.com
A lot of this was figured out through trial and error - i don't have explanations as to why only port 465 works with
smtp-relay.gmail.com
and / or why the TLS encryption option has no effect on SMTP.As to whether this is a Supabase Auth bug, i highly doubt that it is because we use the native golang smtp library . If anyone still has issues getting google SMTP to work, i would recommend to switch to one of these SMTP providers:
Beta Was this translation helpful? Give feedback.
All reactions