SMTP 535 Authentication Failed — Brevo credentials rejected on /recover endpoint
authHi everyone, I'm currently getting a consistent 535 5.7.8 Authentication failed error when Supabase attempts to send password recovery emails via our custom SMTP provider (Brevo).
Error from Auth logs: "error":"535 5.7.8 Authentication failed" "msg":"500: Error sending recovery email" "path":"/recover"
What I've tried: Regenerated SMTP key multiple times Tested ports 587 and 465, Verified username is the exact Brevo login email Confirmed with Brevo support there are no blocks on their side Brevo confirmed credentials are correct and Brevo's response: No blocks on their account. Credentials are valid. The issue appears to be on the Supabase side rejecting or incorrectly passing the credentials to Brevo's SMTP relay.
Has anyone had similar issues with how the SMTP credentials are being stored or passed, or if there are any known issues with Brevo SMTP integration on the supabase platform (free plan)?
Appreciate any feedback on this.
Error from Auth logs: "error":"535 5.7.8 Authentication failed" "msg":"500: Error sending recovery email" "path":"/recover"
What I've tried: Regenerated SMTP key multiple times Tested ports 587 and 465, Verified username is the exact Brevo login email Confirmed with Brevo support there are no blocks on their side Brevo confirmed credentials are correct and Brevo's response: No blocks on their account. Credentials are valid. The issue appears to be on the Supabase side rejecting or incorrectly passing the credentials to Brevo's SMTP relay.
Has anyone had similar issues with how the SMTP credentials are being stored or passed, or if there are any known issues with Brevo SMTP integration on the supabase platform (free plan)?
Appreciate any feedback on this.
