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

MailerSend: support extra headers

Browse Source 
MailerSend added a `"headers"` API field
(which is available to "Enterprise
accounts only").
This commit is contained in:
Mike Edmunds
2024-06-21 17:41:33 -07:00
parent 0776b12331
commit faf98c22d7
5 changed files with 34 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/esps/mailersend.rst
View File

@@ -204,7 +204,12 @@ see :ref:`unsupported-features`.
Anymail will use only the first one.
**Limited extra headers**
MailerSend does not allow most extra headers. There are two exceptions:
MailerSend allows extra email headers for "Enterprise accounts only."
If you try to send :ref:`extra headers <message-headers>` with a non-enterprise
account, you may receive an API error.
However, MailerSend has special handling for two headers,
and *any* MailerSend account can send messages with them:
* You can include :mailheader:`In-Reply-To` in extra headers, set to
a message-id (without the angle brackets).
@@ -216,8 +221,11 @@ see :ref:`unsupported-features`.
if your extra headers have :mailheader:`Precedence` set to ``"bulk"`` or
``"list"`` or ``"junk"``, or ``false`` for any other value.
Any other extra headers will raise an
:exc:`~anymail.exceptions.AnymailUnsupportedFeature` error.
.. versionchanged:: 11.0
In earlier releases, attempting to send other headers
(even with an enterprise account) would raise an
:exc:`~anymail.exceptions.AnymailUnsupportedFeature` error.
**No merge headers support**
MailerSend's API does not provide a way to support Anymail's