Conversation
|
Sorry for the noise, I decided to update the documentation as well. I don't plan to push anything else unless I find an error or you request changes. I did test this locally with resend and I am receiving emails, using a secret and signing key. |
| Then, if you are using Resend's webhook signature validation (with svix), | ||
| add the webhook signing secret to your Anymail settings: |
There was a problem hiding this comment.
I would maybe note that this is the same RESEND_SIGNING_SECRET used for tracking webhooks, so if you're using both you only need to configure it once.
There was a problem hiding this comment.
Hmm, I did a quick test, if I add a second webhook URL in resend.com, it is assigned a DIFFERENT signing secret. So if you use both (because the events triggering the webhooks differ) then you actually need TWO signing secrets.
tests/test_resend_inbound.py
Outdated
| raw_mime = ( | ||
| "From: Sender Name <from@example.com>\r\n" | ||
| "To: recipient@example.org\r\n" | ||
| "Subject: Testing Resend inbound\r\n" | ||
| "Date: Thu, 22 Feb 2024 23:41:11 +0000\r\n" | ||
| "Message-ID: <ABCDE12345@mail.example.com>\r\n" | ||
| "MIME-Version: 1.0\r\n" | ||
| "Content-Type: multipart/alternative; boundary=boundary\r\n" | ||
| "\r\n" | ||
| "--boundary\r\n" | ||
| "Content-Type: text/plain\r\n" | ||
| "\r\n" | ||
| "Hello, world!\r\n" | ||
| "--boundary\r\n" | ||
| "Content-Type: text/html\r\n" | ||
| "\r\n" | ||
| "<p>Hello, world!</p>\r\n" | ||
| "--boundary--\r\n" | ||
| ) |
There was a problem hiding this comment.
This is a style choice, but other Anymail tests typically use dedent("""\ ... """).replace("\n", "\r\n") (with a single triple-quoted string) to make inlined mime a little more readable: example.
|
Closes #464. |
2 participants
Added inbound handling for Resend.
https://resend.com/docs/dashboard/receiving/introduction