mirror of
https://github.com/pacnpal/django-anymail.git
synced 2025-12-20 03:41:05 -05:00
Docs: update tooling and outdated/broken content
* Update docs build config
* Specify Sphinx and theme versions in docs/requirements.txt
(tox had been using latest; RTD had pinned older versions)
* Update docs builds for Python 3 and recent Sphinx
* Remove obsolete sphinx-rtd-theme patches
* Add .readthedocs.yml
* Move some JS to async (now that Sphinx supports that)
* Fix version-alert.js for async loading
* Remove docs versionadded/changed info older than v3.0
* Fix broken GitHub issue links in changelog (never worked?)
* Add setup long_description_content_type
* Drop poorly maintained AUTHORS.txt
(just point to GitHub contributors page)
This commit is contained in:
@@ -13,8 +13,6 @@ AWS SDK for Python, and includes sending, tracking, and inbound receiving capabi
|
||||
Depending on your needs, one of them may be more appropriate than Anymail.
|
||||
|
||||
|
||||
.. versionadded:: 2.1
|
||||
|
||||
.. _Amazon Simple Email Service: https://aws.amazon.com/ses/
|
||||
.. _Boto 3: https://boto3.readthedocs.io/en/stable/
|
||||
|
||||
|
||||
@@ -137,13 +137,6 @@ use Anymail's :attr:`~anymail.message.AnymailMessage.envelope_sender`
|
||||
message.envelope_sender = "anything@mail2.example.com" # the "anything@" is ignored
|
||||
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
Earlier Anymail versions looked for a special `sender_domain` key in the message's
|
||||
:attr:`~anymail.message.AnymailMessage.esp_extra` to override Mailgun's sender domain.
|
||||
This is still supported, but may be deprecated in a future release. Using
|
||||
:attr:`~anymail.message.AnymailMessage.envelope_sender` as shown above is now preferred.
|
||||
|
||||
.. _Mailgun sender domain:
|
||||
https://help.mailgun.com/hc/en-us/articles/202256730-How-do-I-pick-a-domain-name-for-my-Mailgun-account-
|
||||
|
||||
|
||||
@@ -5,8 +5,6 @@ Mailjet
|
||||
|
||||
Anymail integrates with the `Mailjet`_ email service, using their transactional `Send API`_ (v3).
|
||||
|
||||
.. versionadded:: 0.11
|
||||
|
||||
.. _mailjet-v31-api:
|
||||
|
||||
.. note::
|
||||
|
||||
@@ -257,14 +257,6 @@ for each event in the batch.)
|
||||
https://mandrill.zendesk.com/hc/en-us/articles/205583197-Inbound-Email-Processing-Overview
|
||||
|
||||
|
||||
.. versionchanged:: 1.3
|
||||
Earlier Anymail releases used :samp:`.../anymail/mandrill/{tracking}/` as the tracking
|
||||
webhook url. With the addition of inbound handling, Anymail has dropped "tracking"
|
||||
from the recommended url for new installations. But the older url is still
|
||||
supported. Existing installations can continue to use it---and can even install it
|
||||
on a Mandrill *inbound* route to avoid issuing a new webhook key.
|
||||
|
||||
|
||||
.. _migrating-from-djrill:
|
||||
|
||||
Migrating from Djrill
|
||||
@@ -380,8 +372,6 @@ Changes to EmailMessage attributes
|
||||
instead. You'll need to pass a valid email address (not just a domain),
|
||||
but Anymail will use only the domain, and will ignore anything before the @.
|
||||
|
||||
.. versionchanged:: 2.0
|
||||
|
||||
**Other Mandrill-specific attributes**
|
||||
Djrill allowed nearly all Mandrill API parameters to be set
|
||||
as attributes directly on an EmailMessage. With Anymail, you
|
||||
|
||||
Reference in New Issue
Block a user