medmunds b664ee3dbc SparkPost: work around json recipients problem ...

python-sparkpost generates a transmissions.send
payload which is now considered invalid by the API,
if you try to use both `cc` (or `bcc`) and the
`recipients` dict structure required for merge_data.

[Anymail had been generating that recipients dict
structure in all cases, for simplicity. Sometime
between 2016-06-07 and 2016-06-22, SparkPost
began rejecting that if it appeared in the `header_to`
constructed by python-sparkpost.]

2016-06-22 16:58:56 -07:00

..

__init__.py

Fork from Djrill and rename to "anymail"

2016-02-27 11:16:04 -08:00

base_requests.py

Upgrade requests exceptions to AnymailRequestsAPIError

2016-06-01 10:18:27 -07:00

base.py

Add pre_send and post_send signals

2016-05-12 21:18:04 -07:00

mailgun.py

Add ESP templates, batch send and merge

2016-05-06 12:27:11 -07:00

mandrill.py

Mandrill: support esp_extra

2016-05-11 15:08:57 -07:00

postmark.py

Add ESP templates, batch send and merge

2016-05-06 12:27:11 -07:00

sendgrid.py

SendGrid: set to to from in batch send.

2016-06-01 08:05:51 -07:00

sparkpost.py

SparkPost: work around json recipients problem

2016-06-22 16:58:56 -07:00

test.py

Use generic TestBackend for base functionality tests

2016-05-12 17:18:48 -07:00