Question

I am currently trying to integrate mandrill into this Django-based website for emails. Djrill is the recommended package for Django and sits in place of the default SMTP/email backend, passing emails through to a Mandrill account.

When I try to test that this new backend is working by running this command:

send_mail('Test email', body, 'noreply@*********.com', [user.email], fail_silently=False)

It throws the following error: http://pastebin.ca/2239978

Can anybody point me to my mistake?

Answer 1

Update:

As @DavidRobinson mentions in a comment, you are not getting a successful response from the mandrill API authentication call. You should double check your API key.

If that is correct, try using curl to post {"key": <your api key>, "email": <your from email>} to MANDRILL_API_URL + "/users/verify-sender.json" and see if you get a 200.

Something like this:

curl -d key=1234567890 -d email=[e-mail] http://mandrill.whatever.com/user/verify-sender.json

Original answer:

There is also an issue in Djrill that prevents a useful error message from propagating up. That last line of the stack trace is the problem.

This is the entire open method taken from the source:

def open(self, sender):
    """
    """
    self.connection = None

    valid_sender = requests.post(
        self.api_verify, data={"key": self.api_key, "email": sender})

    if valid_sender.status_code == 200:
        data = json.loads(valid_sender.content)
        if data["is_enabled"]:
            self.connection = True
            return True
    else:
        if not self.fail_silently:
            raise

See how it just says raise without an exception argument? That syntax is only allowed inside an except block, and raises the exception currently being handled. It doesn’t work outside an except block.

An open issue in Djrill mentions a send failure and links a fork that supposedly fixes it. I suspect Djrill isn’t well supported and you might try that fork or another solution entirely.