From 651292fd249bf3a410a968c046f0e80c0a08e6c6 Mon Sep 17 00:00:00 2001 From: medmunds Date: Wed, 13 May 2015 17:58:55 -0700 Subject: [PATCH] Note Django DEFAULT_FROM_EMAIL in docs. Ref https://github.com/brack3t/Djrill/issues/69#issuecomment-74062569 --- README.rst | 5 +++-- docs/installation.rst | 5 +++++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index d97f40d..4ef012b 100644 --- a/README.rst +++ b/README.rst @@ -24,7 +24,7 @@ In general, Djrill "just works" with Django's built-in `django.core.mail` package. It includes: * Support for HTML, attachments, extra headers, and other features of - `Django's built-in email `_ + `Django's built-in email `_ * Mandrill-specific extensions like tags, metadata, tracking, and MailChimp templates * Optional support for Mandrill inbound email and other webhook notifications, via Django signals @@ -73,9 +73,10 @@ Djrill 1-2-3 MANDRILL_API_KEY = "" EMAIL_BACKEND = "djrill.mail.backends.djrill.DjrillBackend" + DEFAULT_FROM_EMAIL = "you@example.com" # if you don't already have this in settings -3. Now the regular `Django email functions `_ +3. Now the regular `Django email functions `_ will send through Mandrill: .. code-block:: python diff --git a/docs/installation.rst b/docs/installation.rst index e8e0649..822a473 100644 --- a/docs/installation.rst +++ b/docs/installation.rst @@ -35,6 +35,11 @@ In your project's :file:`settings.py`: EMAIL_BACKEND = "djrill.mail.backends.djrill.DjrillBackend" +Also, if you don't already have a :setting:`DEFAULT_FROM_EMAIL` in settings, +this is a good time to add one. (Django's default is "webmaster@localhost", +which won't work with Mandrill.) + + Mandrill Webhooks (Optional) ----------------------------