Pro ticket open since 19 Sep, Auth emails delivered with HTML stripped, needs Auth team escalation

[stphnchshr]

Ticket: #SU-478743
Plan: Pro Plan
Raised: 19 September 2026, via dashboard
Status: No workable response in ~4 weeks. Forwarded to "the respective team" on 25 Sep; latest reply (6 Oct) suggested changing SMTP provider, which was already ruled out in the original ticket.

Issue
Auth emails (custom SMTP via SMTP2GO) arrive with every HTML tag removed. This is blocking production email.

What's been ruled out

• Template is stored verbatim (confirmed via Management API GET /v1/projects/{ref}/config/auth, full <table>, inline styles and {{ .ConfirmationURL }} present)
• Same SMTP host, port and credentials deliver the identical HTML intact via direct SMTP relay and via SMTP2GO's API
• No Auth Hooks configured
• Open/click tracking disabled on the SMTP user

Why this points to Auth, not SMTP
Delivered message has Content-Type: text/html but no tags, and still contains & entities in the confirmation URL. The Go template renderer ran, then markup was removed after rendering. That can only happen inside Auth.

Could a moderator please help get this to the Auth team? Project ref is in the ticket.

[k1ng-arthur]

it seems like you were already with the right team and talking with support, did you reply on the 6th of October to them? Usually all mods/community support can do i get you placed in the right queue and make sure your ticket is not lost.

[stphnchshr]

Hi, yes I replied straight away and pointed out that the SMTP provider had already been ruled out. Unfortunately I haven't heard anything since then.

[tuyakhov]

Agree with your read. The & in the link shows Auth's html/template rendering ran, so the tags were removed after that, before SMTP2GO got the message. Switching provider probably won't fix that.

While the ticket waits, you can use the Send Email hook. With the hook enabled, Auth calls your function instead of using SMTP at all. The function can send through SMTP2GO's API, which already delivers your HTML intact.

One catch: the hook gives you token data, not the rendered email. So your template moves into the function, and you rebuild the link yourself:

${SUPABASE_URL}/auth/v1/verify?token=${token_hash}&type=${email_action_type}&redirect_to=${redirect_to}

I built SenderKit’s Supabase integration after running into Supabase auth email issues myself. It can be the hook target if you'd rather not maintain the function. You can also implement the hook manually of course.