Skip to main content

FogBugz Middleware for Django

Project description

By default, Django sends emails for 500 errors. Simply directing these emails to go to FogBugz can be problematic: FogBugz will attempt to respond to the email, which will fail if you are sending messages from, e.g., FogBugz then generates a case for the failed email.

The solution is to use FogBugz’ ScoutSubmit functionality, which is explicitly designed to handle this situation. ScoutSubmit not only won’t send the bogus response emails; it also allows you to customize which project, area, and assignee to use for the bugs, and allows automatically coalescing these bugs based on their descriptions.


Simply run python install, as you would for any other Python project.


First, you’ll need to set up some parameters for FogBugzMiddleware to work. These settings are:

FOGBUGZ_URL: URL of ScoutSubmit. For Windows-based FogBugz installs, including FogBugz On Demand, this will be http://path/to/fogbugz/scoutSubmit.asp. For Unix-based installs, this will be http://path/to/fogbugz/scoutSubmit.php. FOGBUGZ_USERNAME: User to assign the case to. FOGBUGZ_PROJECT: Project to assign the case to. FOGBUGZ_AREA: Project area to assign the case to. Next, add FogBugzMiddleware to MIDDLEWARE_CLASSES in


That’s it.


Report bugs and submit feature requests at

Project details

Release history Release notifications

This version
History Node


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date (2.3 kB) Copy SHA256 hash SHA256 Source None Dec 15, 2010

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page