pacnpal/django-anymail
1
0
Fork 0
mirror of https://github.com/pacnpal/django-anymail.git synced 2025-12-20 03:41:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

Docs: clarify use of Mailgun's inbound "raw MIME" option

Browse Source 
Refs #389
This commit is contained in:
Mike Edmunds
2024-08-07 15:05:21 -07:00
parent 7779920e9b
commit 9d4fb5daf9
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/esps/mailgun.rst
View File

@@ -556,16 +556,19 @@ forwarding url) with Mailgun inbound routing.
.. note:: .. note::
Anymail also supports Mailgun's "fully-parsed" inbound message format, but the "raw MIME" Anymail supports both of Mailgun's "fully-parsed" and "raw MIME" inbound
version is preferred to get the most accurate representation of any received email. message formats. The raw MIME version is preferred to get the most accurate
Using raw MIME also avoids a limitation in Django's :mimetype:`multipart/form-data` handling representation of any received email. Using raw MIME also avoids a limitation
that can strip attachments with certain filenames (and inline images without filenames). in Django's :mimetype:`multipart/form-data` handling that can strip attachments
with certain filenames (and inline images without filenames).
To use Mailgun's fully-parsed format, change :samp:`.../inbound_mime/` to just * To use raw MIME (recommended), the route forwarding url should end with
:samp:`.../inbound/` at the end of the route forwarding url. :samp:`…/inbound_mime/` as shown above.
* To use fully-parsed format (not recommended), omit the :samp:`_mime` so
the route forwarding url ends with just :samp:`…/inbound/`.
.. versionchanged:: 8.6 .. versionchanged:: 8.6
Using Mailgun's full-parsed (not raw MIME) inbound message format is no longer recommended. Using Mailgun's fully-parsed inbound message format is no longer recommended.
.. _Receiving, Forwarding and Storing Messages: .. _Receiving, Forwarding and Storing Messages: