Django email backends and webhooks for Amazon SES, Brevo (Sendinblue), MailerSend, Mailgun, Mailjet, Postmark, Postal, Resend, SendGrid, SparkPost, Unisender Go and more
This is due to a Resend API change sometime between 2023-12-07 and 2023-12-14. Previously, Resend responded with a helpful "API key is invalid" 403 error—and this is still Resend's documented behavior). But now, Resend's API simply ignores bad/expired/missing API keys and never responds, leading to the timeout.
[This isn't Anymail's bug, but was caught by our integration tests. The new behavior has been reported to Resend. Test disabled in 2cadb949cd7a965116bb1848bcf09631c218cf8a (hopefully temporarily).]
[If you get a
ReadTimeout
trying to send through Resend.com, it could be an invalid API key.]If your
ANYMAIL
settingRESEND_API_KEY
is wrong (or expired), trying to send a message will result aReadTimeout
error (near the end of the stack):This is due to a Resend API change sometime between 2023-12-07 and 2023-12-14. Previously, Resend responded with a helpful "API key is invalid" 403 error—and this is still Resend's documented behavior). But now, Resend's API simply ignores bad/expired/missing API keys and never responds, leading to the timeout.
[This isn't Anymail's bug, but was caught by our integration tests. The new behavior has been reported to Resend. Test disabled in 2cadb949cd7a965116bb1848bcf09631c218cf8a (hopefully temporarily).]