.. _supported-esps: Supported ESPs ============== Anymail currently supports these Email Service Providers. Click an ESP's name for specific Anymail settings required, and notes about any quirks or limitations: .. these are listed in alphabetical order .. toctree:: :maxdepth: 1 mailgun mailjet mandrill postmark sendgrid sendinblue sparkpost Anymail feature support ----------------------- The table below summarizes the Anymail features supported for each ESP. .. currentmodule:: anymail.message ============================================ =========== ========== =========== ========== ========== ============ =========== Email Service Provider |Mailgun| |Mailjet| |Mandrill| |Postmark| |SendGrid| |SendinBlue| |SparkPost| ============================================ =========== ========== =========== ========== ========== ============ =========== .. rubric:: :ref:`Anymail send options ` ------------------------------------------------------------------------------------------------------------------------------------- :attr:`~AnymailMessage.envelope_sender` Domain only Yes Domain only No No No Yes :attr:`~AnymailMessage.metadata` Yes Yes Yes No Yes Yes Yes :attr:`~AnymailMessage.send_at` Yes No Yes No Yes No Yes :attr:`~AnymailMessage.tags` Yes Max 1 tag Yes Max 1 tag Yes Max 1 tag Max 1 tag :attr:`~AnymailMessage.track_clicks` Yes Yes Yes Yes Yes No Yes :attr:`~AnymailMessage.track_opens` Yes Yes Yes Yes Yes No Yes .. rubric:: :ref:`templates-and-merge` ------------------------------------------------------------------------------------------------------------------------------------- :attr:`~AnymailMessage.template_id` No Yes Yes Yes Yes Yes Yes :attr:`~AnymailMessage.merge_data` Yes Yes Yes No Yes No Yes :attr:`~AnymailMessage.merge_global_data` (emulated) Yes Yes Yes Yes Yes Yes .. rubric:: :ref:`Status ` and :ref:`event tracking ` ------------------------------------------------------------------------------------------------------------------------------------- :attr:`~AnymailMessage.anymail_status` Yes Yes Yes Yes Yes Yes Yes |AnymailTrackingEvent| from webhooks Yes Yes Yes Yes Yes *Coming* Yes .. rubric:: :ref:`Inbound handling ` ------------------------------------------------------------------------------------------------------------------------------------- |AnymailInboundEvent| from webhooks Yes Yes Yes Yes Yes No Yes ============================================ =========== ========== =========== ========== ========== ============ =========== Trying to choose an ESP? Please **don't** start with this table. It's far more important to consider things like an ESP's deliverability stats, latency, uptime, and support for developers. The *number* of extra features an ESP offers is almost meaningless. (And even specific features don't matter if you don't plan to use them.) .. |Mailgun| replace:: :ref:`mailgun-backend` .. |Mailjet| replace:: :ref:`mailjet-backend` .. |Mandrill| replace:: :ref:`mandrill-backend` .. |Postmark| replace:: :ref:`postmark-backend` .. |SendGrid| replace:: :ref:`sendgrid-backend` .. |SendinBlue| replace:: :ref:`sendinblue-backend` .. |SparkPost| replace:: :ref:`sparkpost-backend` .. |AnymailTrackingEvent| replace:: :class:`~anymail.signals.AnymailTrackingEvent` .. |AnymailInboundEvent| replace:: :class:`~anymail.signals.AnymailInboundEvent` Other ESPs ---------- Don't see your favorite ESP here? Anymail is designed to be extensible. You can suggest that Anymail add an ESP, or even contribute your own implementation to Anymail. See :ref:`contributing`.