Tim Abbott

@zivarg if `send_test_email` is working and other emails are not I suspect the issue is the second bullet here: http://zulip.readthedocs.io/en/latest/production/email.html#troubleshooting (Basically, that we send from a noreply email). Can you...

I think this is fine, but one thing worth noting is that we do often here from users who have university IT systems that are running an old version of...

I suspect they don't have root on their old RHEL 6 system and it didn't come with Python 3 installed. But I don't know for sure, as they didn't reply...

It looks like the README.md for this project already documents options for older Python; we should njust copy a version of that to the zulip.com/api/ content as well.

https://github.com/zulip/docker-zulip/wiki has a few articles. I think: * the "management commands" one we should move into a section of `README.md`. * https://github.com/zulip/docker-zulip/wiki/Proxying-via-nginx-on-host-machine should be merged as supplemental notes in https://zulip.readthedocs.io/en/latest/production/deployment.html...

Transferring the issue to `docker-zulip`, since it seems likely to somehow be docker specific.

(As noted in the chat.zulip.org thread, we are already using `RawConfigParser`, so that isn't the problem.)

Yeah, we should probably just import the full set of things that are useful in `prod_settings_template.py` to avoid this. @hackerkid FYI.

Agreed, we should have that. You can do that by removing everything in `/opt/docker` after shutting down the containers.

I think my first pass strategy for handling the "error emails" problem would be to modify the content of our error emails to link to a "troubleshooting exceptions" docs page,...