Re: postscreen_upstream_proxy_protocol with both proxied and unproxied clients

We solved this problem by enabling postscreen on port 26, and forwarding port 25 on the ELB to port 26 on the instance, with Proxy Protocol enabled. This allows our local clients to connect as normal via port 25 direct to the instance, and remote incoming mail to be processed by postscreen.

Re: postscreen_upstream_proxy_protocol with both proxied and unproxied clients

--On Friday, June 24, 2016 12:26 PM -0400 Wietse Venema wrote: I suppose that one could configure a namaddr_list (and use IP address patterns only) that skips the haproxy protocol handshake. Ok, the problem is I have no way of knowing what clients will come in via the

Re: postscreen_upstream_proxy_protocol with both proxied and unproxied clients

Wietse Venema: > Quanah Gibson-Mount: > > We recently deployed into AWS, and were following > > . > > > > However, we found that if we set postscreen_upstream_proxy_protocol=haproxy > > we are then no longer able to

Re: postscreen_upstream_proxy_protocol with both proxied and unproxied clients

Quanah Gibson-Mount: > We recently deployed into AWS, and were following > . > > However, we found that if we set postscreen_upstream_proxy_protocol=haproxy > we are then no longer able to connect directly to the MTAs to

postscreen_upstream_proxy_protocol with both proxied and unproxied clients

We recently deployed into AWS, and were following . However, we found that if we set postscreen_upstream_proxy_protocol=haproxy we are then no longer able to connect directly to the MTAs to send mail. Is there any