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: remove references to future inbound handling

Browse Source 
(Postponed -- see discussion or vote to reopen in #4)

[ci skip]
This commit is contained in:
medmunds
2016-11-01 11:46:49 -07:00
parent 1cced97f65
commit e78410eea4
7 changed files with 4 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/esps/index.rst
View File

@@ -50,10 +50,6 @@ Email Service Provider |Mailgun| |Mandrill| |Postmark|
============================================ ========== ========== ========== ========== ===========
.. .. rubric:: :ref:`inbound`
.. -------------------------------------------------------------------------------------------
.. Inbound webhooks (coming)...
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

5
docs/esps/mandrill.rst
View File

@@ -374,8 +374,9 @@ parameters is that most logging and analytics systems are aware of the
need to keep auth secret.)
Anymail replaces `djrill.signals.webhook_event` with
`anymail.signals.tracking` and (in a future release)
`anymail.signals.inbound`. Anymail parses and normalizes
`anymail.signals.tracking` for delivery tracking events.
(It does not currently handle inbound message webhooks.)
Anymail parses and normalizes
the event data passed to the signal receiver: see :ref:`event-tracking`.
The equivalent of Djrill's ``data`` parameter is available