Databases
StackOverflow2013
Postsdbo
PODebugging 500 on incoming Mail on Heroku from Mailgun
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODebugging 500 on incoming Mail on Heroku from Mailgun
    primarykey
    data
    text
    <p>I'm trying to debug a view which gets an incoming mail from Mailgun to a Django installation on Heroku.</p> <p>The view itself is directly taken from the Mailgun docs and if I manually call the URL then I get an OK response.</p> <pre><code>@csrf_exempt def askfriend_emailresponse(request): from_email = "..." to_email = "..." if request.method == 'POST': sender = request.POST.get('sender') recipient = request.POST.get('recipient') answer = request.POST.get('stripped-text', '') try: send_mail("inside post"+str(recipient[recipient.find("+")+1:recipient.find("@")]), answer, from_email, to_email) except Exception, e: raise e return HttpResponse('OK') </code></pre> <p>Also, if I just place a post to that URL through an external tool (I'm using Poster for this purpose) I can get the 200 (I had to add the <code>@csrf_exempt</code> for that but that's fine for now).</p> <p>However, from the Mailgun logs I see that there is a 500 Error when forwarding the message and from Heroku I see there is an incoming request causing a 500:</p> <pre><code>2013-03-13T09:59:04+00:00 heroku[router]: at=info method=POST path=[url] host=[hostname].herokuapp.com fwd="198.61.253.112" dyno=web.1 queue=0 wait=0ms connect=1ms service=86ms status=500 bytes=102194 </code></pre> <p>My questions after spending more than a day researching:</p> <p>1) Any idea what could be wrong (would be nice) - and at least as important</p> <p>2) How can I properly test this? Because Mailguns logs are very brief (500 - that's it!) and Heroku also doesn't really help there... Also, having to always deploy to Heroku first obviously is quite slow, hence, I'm wondering if that really is the "smart" way to develop... (all other things I obviously test locally but with an external e-mail coming through a POST through Mailgun I don't know how to test that locally)</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScyroxx
    1. USJonas
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODebugging 500 on incoming Mail on Heroku from Mailgun
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. PODebugging 500 on incoming Mail on Heroku from Mailgun
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat does your Django configuration look like? I made a little helper for configuring Sendgrid and/or Mailgun on Heroku right from the environment: https://github.com/fubaz/djheroku/blob/master/djheroku/conf.py#L77
      singulars
      1. PODebugging 500 on incoming Mail on Heroku from Mailgun
      1. USferrix
    2. COAlso, The title is talking about incoming mail and send_mail looks like outgoing to me.
      singulars
      1. PODebugging 500 on incoming Mail on Heroku from Mailgun
      1. USferrix
    3. COThanks - the send_mail is actually was just for me a kind of "notification message" that everything is fine - I could probably also instead output to a log file, just thought sending some simple message might be easier. Also - sending mail works properly in other parts of the system - hence, not sure if it is an environment problem (your config file looks very similar to mine)
      singulars
      1. PODebugging 500 on incoming Mail on Heroku from Mailgun
      1. USJonas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload