medmunds
fed98b14a8
install: remove need to name [esp]
...
Simplify install to just `pip install django-anymail`.
(Rather than `... django-anymail[mailgun]`
All of the ESPs so far require requests, so just move
that into the base requirements. (Chances are your
Django app already needs requests for some other
reason, anyway.)
Truly unique ESP dependencies (e.g., boto for
AWS-SES) could still use the setup extra features
mechanism.
2016-03-14 13:26:06 -07:00
medmunds
b6bbdf4791
The *package* name is "django-anymail"
...
(not just "anymail")
2016-03-09 20:27:44 -08:00
medmunds
1e80c3ec37
Invert unsupported-features setting
...
Change from UNSUPPORTED_FEATURE_ERRORS
(default True) to IGNORE_UNSUPPORTED_FEATURES
(default False). Parallels IGNORE_RECIPIENT_STATUS.
2016-03-09 18:47:42 -08:00
medmunds
20c6350140
Update (almost) all the docs
2016-03-09 18:37:11 -08:00
medmunds
9971c1780f
Document MANDRILL_API_URL
2015-12-02 16:10:29 -08:00
medmunds
aa46fadb48
Clean up global MANDRILL_SETTINGS
...
* Clean up Djrill backend __init__
* Fold MANDRILL_SUBACCOUNT into
global_settings logic
* Add some missing override tests
* Update docs
2015-12-02 15:58:23 -08:00
medmunds
d14b87c910
Raise error for invalid/rejected recipients
...
Raise new MandrillRecipientsRefused exception
when Mandrill returns 'reject' or 'invalid' status
for *all* recipients of a message.
(Similar to Django's SMTP email backend raising
SMTPRecipientsRefused.)
Add setting MANDRILL_IGNORE_RECIPIENT_STATUS
to override the new exception.
Trap JSON parsing errors in Mandrill API response,
and raise MandrillAPIError for them. (Helps with #93.)
Closes #80 .
Closes #81 .
2015-12-01 13:26:21 -08:00
medmunds
99ac099081
Remove DjrillAdminSite
...
Closes #78
2015-05-14 11:00:52 -07:00
medmunds
651292fd24
Note Django DEFAULT_FROM_EMAIL in docs.
...
Ref https://github.com/brack3t/Djrill/issues/69#issuecomment-74062569
2015-05-13 17:58:55 -07:00
medmunds
8ab36d2cd0
Django 1.8 alpha 1 support
...
* Test on Python 2.7, 3.4, pypy.
* Call super.setUpClass in DjrillAdminTests.
https://docs.djangoproject.com/en/dev/releases/1.8/#overriding-setupclass-teardownclass-in-test-cases
Also clear up some new PendingDeprecationWarnings, where
the changes can easily remain compatible back to Django 1.3:
* Remove deprecated django.conf.urls.patterns.
(And match Django recommendations in our docs.)
https://docs.djangoproject.com/en/dev/releases/1.8/#django-conf-urls-patterns
* Remove deprecated SimpleTestCase.urls.
(We've already back-ported @override_settings
for testing older Django versions.)
https://docs.djangoproject.com/en/dev/releases/1.8/#django-test-simpletestcase-urls
2015-01-16 16:17:31 -08:00
medmunds
c6b171b671
Document Django 1.7 admin installation changes.
...
Closes #74 .
2014-09-29 14:44:22 -07:00
medmunds
ba2302ae56
Subaccounts: Document setting; verify message option overrides global setting
2014-04-20 12:57:08 -07:00
medmunds
c3da043260
Document webhook support
2013-04-17 16:02:29 -07:00
medmunds
28538a5391
Docs: break apart the lengthy readme into organized docs
...
Also sphinx-ify where appropriate, and lots of general cleanup/editing.
2013-03-04 20:24:26 -08:00
