Menu

📰
0

Best modern way to handle transactional emails? (Struggling with Google Workspace/OAuth2)

Reddit r/django·u/anhedonix·about 1 month ago
#3Q05jW3y
Reading 0:00
15s threshold

Best modern way to handle transactional emails? (Struggling with Google Workspace/OAuth2) Hi everyone, I’m setting up a Django app and need to send standard transactional emails (account activation, password resets, etc.) from my custom domain. Currently, my domain email is hosted on Google Workspace. The roadblock: \- I've been trying to set this up using OAuth2, but I’m running into walls. Most of the tutorials I find are heavily outdated, or the API tokens I generate have a very short lifespan and are a nightmare to manage automatically. **What I'm looking for:** I’m not looking for anyone to write the code for me, just a push in the right direction or some updated documentation/resources. Specifically: \- Is there a modern, standard way to handle Google Workspace OAuth2 in Django without the token lifespan issues? \- Alternatively: I am completely open to using a transactional email service (like Resend, SendGrid, Mailgun, etc.) as long as the emails still come from my custom domain.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More