search

brack3t / Djrill

[INACTIVE/UNMAINTAINED] Djrill is an email backend and new message class for Django users that want to take advantage of the Mandrill transactional email service from MailChimp.
BSD 3-Clause "New" or "Revised" License
319 stars 64 forks source link

Add documentation for Heroku #35

Closed hoorzad closed 11 years ago

hoorzad commented 11 years ago

Mandrill is available as a Heroku add-on. Could you possibly provide some information regarding using Djrill on that platform.

You said in your documentation that we should "be sure to use a from_email that's in one of your Mandrill approved sending domains, or the message won't get sent". Their Heroku docs doesn't say anything about approved domains, but the example[1] uses a 'heroku.com' domain.

Does it mean that I can use any '@heroku.com' from address if my app URL is a heroku subdomain and I can use any @.com if my app is on a cusom domain? How can I set DEFAULT_FROM_EMAIL correctly?

[1] https://devcenter.heroku.com/articles/mandrill#example

waltonryan commented 11 years ago

I was able to get djrill up and running with Heroku, without having to include any special sending domains on the Mandrill account. I just used my gmail address in settings.py for DEFAULT_FROM_EMAIL (e.g., DEFAULT_FROM_EMAIL = 'myusername@gmail.com'. It's been up and running now for a couple weeks without issue.

Here's Mandrill's comment on Sending Domains: "Mandrill automatically adds any domain you use for sending through Mandrill. Mandrill also automatically adds authentication to all messages sent through our servers, but adding SPF and DKIM records for your sending domain(s) is strongly recommended for better deliverability."

http://help.mandrill.com/entries/21681347-how-do-i-set-up-sending-domains

hoorzad commented 11 years ago

Thanks.

waltonryan commented 11 years ago

Np. I'm using djrill in a django starter app I'm working on. The code is available at www.eldjango.com.