Supabase Custom SMTP & Edge Function Email Behavior (AWS SES)
I’m using AWS SES with Supabase.
From my understanding, Supabase Custom SMTP applies only to Auth emails and does not affect Edge Functions, which require their own SES integration (API/SMTP).
I’ve:
Configured SES using access key & secret key inside my Edge Function, and it works correctly.
Configured Custom SMTP in Supabase Auth using SES SMTP username and password to send Auth emails (signup and magic link).
Used the same sender details in both cases.
Issue:
When Custom SMTP is enabled in Supabase Auth, the received emails ( from edge function ) show “unverified sender/domain” in the inbox.
When Custom SMTP is disabled, the inbox shows the sender as verified.
Is this expected behavior, or am I missing any SES configuration (SPF/DKIM/MAIL FROM)?
From my understanding, Supabase Custom SMTP applies only to Auth emails and does not affect Edge Functions, which require their own SES integration (API/SMTP).
I’ve:
Configured SES using access key & secret key inside my Edge Function, and it works correctly.
Configured Custom SMTP in Supabase Auth using SES SMTP username and password to send Auth emails (signup and magic link).
Used the same sender details in both cases.
Issue:
When Custom SMTP is enabled in Supabase Auth, the received emails ( from edge function ) show “unverified sender/domain” in the inbox.
When Custom SMTP is disabled, the inbox shows the sender as verified.
Is this expected behavior, or am I missing any SES configuration (SPF/DKIM/MAIL FROM)?
