Hello Wietse, maybe I should tell I am using nginx for all my inbound proxy protocol needs (HA is via multiple addresses in DNS), and my email test service uses proxy protocol outbound as well. Before I picked proxy protocol for that use case I checked SOCKS or HTTP proxies but perceived the complexity significantly higher than with proxy protocol and I already had some proxy protocol code around. My test service doesn´t use pipelining for sure, and my small postfix instance probably also doesn´t benefit a lot doing that.
>I expect that a SOCKS5 client would not use much code, compared to the code >that was needed with HaProxy. I´d like to challenge that. (HA) Proxy protocol essentially implies to connect to another configured address and then prepend a string with connection info to the TCP stream. But I agree, whether proxy protocol or SOCKS is easier to incorporate probably depends more on whether you can reuse some existing client code than on the complexity of the protocol, and what features are hard. With proxy protocol and nginx I think you can in fact do a remote smtp_bind_adddress(6) if needed, but I haven´t tested that so far. If the route were SOCKS5 and disable pipeline, I´d be still interested in that. Joachim _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
