Abhilash Raj

I think it happens because we set the environment variable in docker-compose without quotes (" ") around them and so special characters that bash finds to be useful end up...

Mailman uses `requests` under the hood to `GET` things and according to the [documentation](http://docs.python-requests.org/en/master/user/advanced/#proxies) it should work with Environment Variables. `docker exec -it malman-core bash` should drop you in an...

Ah, thanks about that, I forgot we do su-exec ;) I will investigate the reason why Mailman isn't able to pickup the environment variable.

I am not able to re-produce this issue, atleast in the Mailman-core container. I added the HTTP_PROXY to my `docker-compose.yaml` file: ```yaml version: '2' services: mailman-core: image: maxking/mailman-core:0.1 container_name: mailman-core...

I initially thought that `su-exec` wouldn't be forwarding the environment variables (like usually `sudo` doesn't). However, it looks like all the environment variables persist as expected.

There are conflicts in the changes that you have made, can you please re-base the changes? I recently change the `From:` part to be something `postorius@$SERVE_FROM_DOMAIN` so that it provides...

@ulrith you can create one like this too: ``` docker-compose exec -T mailman-web python manage.py createsuperuser ``` This command is going to be interactive but will work. I will add...

@ulrith Also, getting social logins to work is a little tricky if you are doing it for the first time, let me know and I can help you get started.

@ulrith Sure! We should move to IRC or email?

@almereyda It should not be very difficult to just remove all the social logins. You just change the INSTALLED_APPS to remove all the social logins. There potentially could be an...