Mario Fetka
5897512fd9
Complete the current IMAP, POP3, SMTP and proxy protocol work; add the validated setup and administration UI, packaging examples, tests, and maintained roadmap/documentation for the 0.7 development line.
1.0 KiB
Nginx Proxy Manager
Create one Proxy Host for the Bongo hostname. Use http as the forwarding
scheme, the mail host as the forwarding hostname/IP, and port 8080 when NPM
talks directly to Bongo Web. Enable the public certificate, HTTP/2, and
"Force SSL". Websocket support is harmless but is not required by Bongo 0.7.
In Bongo, select the Nginx Proxy Manager deployment and add only the actual NPM
container/host address or CIDR to web.trusted_proxies. Do not use
0.0.0.0/0. Bongo accepts X-Forwarded-For only while the immediate peer is
trusted, and peels trusted proxy hops from the right side of the chain.
If NPM forwards first to Apache on the mail host and Apache then forwards to
Bongo, configure both NPM's source network and Apache's address as trusted
proxies. Apache must preserve the incoming X-Forwarded-For chain.
NPM's normal Proxy Host is HTTP-only. Publish SMTP, submission, IMAP, POP3,
and ManageSieve with a TCP proxy such as HAProxy and enable Bongo's PROXY
protocol only for that proxy's source network. See haproxy-bongo.cfg.