Probleme Unable to validate spam
Hi everyone,
I’m running into a really frustrating issue with Supabase Auth email templates and I’m wondering if anyone has found a reliable workaround.
Whenever I try to edit any Auth email template in the dashboard (for example the “Invite user” template), saving the template fails with this error:
This happens even if I use an extremely minimal template like:
or even just:
I’ve already tried:
- Resetting the template to default and then editing it again
- Removing all images, extra links, and styling
- Keeping only the built‑in variables like
- Using different subjects and very short bodies
No matter what I do, I still get the same
For email providers, I’ve tested with:
- Resend (as SMTP)
- Hostinger email
Both providers are correctly configured, but the problem happens before the email is even sent, at the Supabase template level when saving in the dashboard.
What I’m trying to achieve:
- Just customize the Auth email templates a bit (mainly copy + simple HTML)
- Ideally still use the built‑in Auth flows (signup, invite, reset, magic link)
Questions:
1. Is this a known bug with the current email template spam validation?
2. Is there any way to completely bypass this validation for hosted projects?
3. For those of you who ran into this, did you end up:
- Leaving the default templates and only using a custom SMTP (Resend / others)?
- Moving everything to a send email hook + Edge Function + Resend API and ignoring the dashboard templates entirely?
Any up‑to‑date guidance or examples would be super appreciated.
Thanks in advance
I’m running into a really frustrating issue with Supabase Auth email templates and I’m wondering if anyone has found a reliable workaround.
Whenever I try to edit any Auth email template in the dashboard (for example the “Invite user” template), saving the template fails with this error:
Failed to validate template: Unable to validate spamThis happens even if I use an extremely minimal template like:
or even just:
I’ve already tried:
- Resetting the template to default and then editing it again
- Removing all images, extra links, and styling
- Keeping only the built‑in variables like
{{ .ConfirmationURL }}- Using different subjects and very short bodies
No matter what I do, I still get the same
Unable to validate spamFor email providers, I’ve tested with:
- Resend (as SMTP)
- Hostinger email
Both providers are correctly configured, but the problem happens before the email is even sent, at the Supabase template level when saving in the dashboard.
What I’m trying to achieve:
- Just customize the Auth email templates a bit (mainly copy + simple HTML)
- Ideally still use the built‑in Auth flows (signup, invite, reset, magic link)
Questions:
1. Is this a known bug with the current email template spam validation?
2. Is there any way to completely bypass this validation for hosted projects?
3. For those of you who ran into this, did you end up:
- Leaving the default templates and only using a custom SMTP (Resend / others)?
- Moving everything to a send email hook + Edge Function + Resend API and ignoring the dashboard templates entirely?
Any up‑to‑date guidance or examples would be super appreciated.
Thanks in advance
