On Tue, Feb 28, 2023 at 06:22:12PM -0500, Sam Varshavchik wrote: > Steve Charmer writes: > > > Feb 28 12:20:04 diggy-ocn-drop imapd-ssl: LOGOUT, > > user=<URL:mailto:m...@mydomain.co>m...@mydomain.co, > > ip=[::ffff:104.xxx.xxx.xxx], > > headers=0, body=0, rcvd=77, sent=330, time=0, starttls=1 ... > > I want to be able to add the public IPv4 address of the remote client > > trying > > to login to courier-imapd ...
> That's because there is nothing that the server can do to determine the > client's real IP address. When NAT is used, as is apparently the case is > here, as far as the server knows that's the IP address where the connection > is coming from, and that's the only IP address that's involved. The real > client IP address is only known to the network proxy. What would it take to have Courier-IMAP support HAProxy Proxy Protocol? https://www.haproxy.com/de/blog/haproxy/proxy-protocol/ Other load balancers use HAProxy's solution as well, it isn't exclusive to them. As as you see in the list, several email component packages already support it. As for a different way to do it, certain Load Balancers can do L4 cut-through load balancing (ie. F5, Avi) preserving the client IP. _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
