reverse proxy documentation and trusted-networks

[plutext]

TLDR: each of the reverse proxy pages should remind the reader they need to configure trusted-networks!

I've successfully created a docker-compose.yaml for putting mail-server behind an haproxy reverse proxy.

For the docker compose setup I worked from https://stalw.art/docs/server/reverse-proxy/traefik

haproxy.cfg came from https://stalw.art/docs/server/reverse-proxy/haproxy

But then I wasted the better part of a day trying to figure out why it didn't work. haproxy was receiving and retransmitting, but the web client would get a 502, and nothing useful in the mail-server logs.

In the process I ended up down https://www.reddit.com/r/stalwartlabs/comments/1hwo0bq/docker_container_blocked_its_own_ip_and_other/ and to workaround that, confusing docker daemon about its bridged subnet. Aaargh.

Turns out the critical information is on the https://stalw.art/docs/server/reverse-proxy/proxy-protocol page.

May I suggest that each of the reverse proxy implementation pages (taefik, haproxy, nginx etc) contain a reminder:

You must also configure Stalwart to trust the source of the proxy connections, or things won't work!

At present, each of those pages reads like a complete "Configuration" recipe, without mentioning that critical missing piece.

It might even help if the server logged that it has received a proxy connection, but no trusted network configured.

Its worth removing these config paint points where possible, since they affect initial impressions and thus broader takeup.