From 6d0374e1ce77c05cdaf8a1c3c55e1ed58e7d2fe8 Mon Sep 17 00:00:00 2001 From: Mike Edmunds Date: Wed, 2 Dec 2020 13:44:30 -0800 Subject: [PATCH] Docs: Note Mailgun inbound requires forward action Clarify that Anymail inbound webhook doesn't support Mailgun's store action. Closes #132 --- docs/esps/mailgun.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/esps/mailgun.rst b/docs/esps/mailgun.rst index 7523d8b..d34e8d3 100644 --- a/docs/esps/mailgun.rst +++ b/docs/esps/mailgun.rst @@ -471,6 +471,8 @@ The *action* for your route will be either: :samp:`forward("https://{random}:{random}@{yoursite.example.com}/anymail/mailgun/inbound/")` :samp:`forward("https://{random}:{random}@{yoursite.example.com}/anymail/mailgun/inbound_mime/")` + * *forward* is required to select Mailgun's "forward" action + (Anymail does not support using the "store" action) * *random:random* is an :setting:`ANYMAIL_WEBHOOK_SECRET` shared secret * *yoursite.example.com* is your Django site @@ -489,7 +491,7 @@ Anymail will verify Mailgun inbound message events using your :setting:`MAILGUN_WEBHOOK_SIGNING_KEY ` Anymail setting. By default, Mailgun's webhook signature provides similar security to Anymail's shared webhook secret, so it's acceptable to omit the -:setting:`ANYMAIL_WEBHOOK_SECRET` setting (and "{random}:{random}@" portion of the +:setting:`ANYMAIL_WEBHOOK_SECRET` setting (and "random:random@" portion of the action) with Mailgun inbound routing.