I had wired up Send Grid and it was working, except half the messages it sent arrived in users’ Junk/Spam folder. So I fiddled with DKIM, SPF and DMARC records… worse than “to no avail”, delivery stopped altogether and (then and now) I get an error. Thought maybe something funky with Send Grid, so I tried switched to https://resend.com , copied the creds into Supabase Custom SMTP, and now I’m in the same spot. “Error sending recovery email ”. Someone, PLEASE , help me troubleshoot this. Is it Rebase, Supabase, Netlify or something else?
Hi, @renefournier. What was the most recent deploy id where the emails where working at least some of the time (but often arriving in users’ Junk/Spam folder)?
So, the problem was not at Netlify, Supabase or Resend per se. (Big surprise.)
An eagle-eyed Brian at Resend helped me identify what turned out to be the root cause. When I had switched from SendGrid and failed to precisely copy-paste one of their DNS entries. For posterity, and to help anyone else who finds themselves in a similar situation:
Hi there,
Happy to work through this with you. I‘m noticing that your domain isn't set-up in Resend yet, which is what's preventing you from using our SMTP service. You'll need to make sure you add and verify the `resend._domainkey.albertawellfinder.com` TXT record, i[t's currently not published](https://resend.com/domains/8de79dba-2444-44ca-8af6-c116c8bf8b0a).
Once that's published, you can select "Restart Verification" and Resend will verify the domain.
From there, you'll then be able to send via SMTP with us.
Let me know if you have any questions on this.
- [Brian](https://resend.com/blog/welcoming-brian-kerr), Customer Success Engineer
tl;dr I missed the period in resend._domainkey.albertawellfinder.com separating resend from _domainkey.
Many thanks, Brian and Resend. You have a new customer for life.
