Bad configurations should raise better error responses
500 Errors are quite opaque in general and hardly of any help to users.
We should be raising more useful errors when Django isn't configured correctly. Maybe we should have an initialization phase which checks for all the required settings so that there aren't any cryptic 500 errors showing up to users.
Things that we have observers people regularly miss:
- Email setup
I am not sure where should this live, perhaps in django-mailman3
instead? We can move this to appropriate project later.