Proxy Protocol Support?

Joachim

Imho proxy protocol is useful if your mailcow server is not directly connected to the internet, but of course you still want to have real IP addresses in all logs/headers and not the IP of your proxy. The obvious alternative is NAT, but that is often limited to IPv4 and also subject to limitations of your routing configuration.

I already succeeded using proxy protocol for postfix - smtp (25) and submission (587) - as that is almost trivial to add to the docker-compose.yml, but adding proxy protocol to dovecot - pop3 and imap - doesn´t appear that well prepared.

Has the mailcow team or anyone else implemented support for proxy protocol?

majorminors

I tried to tag you in a recent help request but it’s saying you’re deleted. Your profile has you posting four days ago, so I am skeptical. I’d love to know if you might be able to shed some light on the postfix proxy protocol. I can’t help you with your Dovecot problem though.

Joachim

majorminors I am alive and receiving notifications. There is no “postfix proxy protocol”. I am using the HA proxy protocol which is a defacto standard and supported by nginx, postfix, dovecot and other applications. I succeeded in exposing all relevant mailcow components via proxy protocol, but I´d definitely like to see this a standard feature in mailcow docker-compose.yml, preferably with a configurable network mask from where to accept proxied connections.

majorminors

I’m suspecting this will not be very helpful to you/you already knew since I was asking you for help on this, but in case you didn’t know, there is a docker override example file included with Mailcow that opens the relevant ports (more detail in my response to you in the forum post I linked earlier). I couldn’t get it working but I assume that’s because I didn’t know what I was doing. But then again, perhaps this indicates that whatever else you wanted included isn’t yet included.