31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Sun Jun 1 11:45:04 2008
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:41 2018
|
|
Subject: [Imap-protocol] Proxy IP forwarding
|
|
In-Reply-To: <1212341451.3904.500.camel@hurina>
|
|
References: <1212341451.3904.500.camel@hurina>
|
|
Message-ID: <0i/azqanypELGcsgZG99yw.md5@lochnagar.oryx.com>
|
|
|
|
Timo Sirainen writes:
|
|
> Has anyone implemented some kind of a IP forwarding extension? So
|
|
> backend servers could see the original IPs instead of the proxy's. So
|
|
> login would go something like:
|
|
>
|
|
> 1 XFORWARD lip 1.2.3.4 lport 143 rip 4.5.6.7 rport 35353
|
|
> 2 LOGIN user pass
|
|
|
|
Login referrals? Cyrus Murder?
|
|
|
|
> I guess I could just implement it like that, but at least trying to be
|
|
> interoperable with another implementation would be nice. :)
|
|
|
|
I've done such things as an administrator on the TCP level, using
|
|
transparent proxying and load balancing. Sufficiently advanced hackery
|
|
is indistinguishable from magic. Sufficiently advanced hackery is
|
|
easily distinguished from a good idea. (Login referrals IMO have the
|
|
same characteristics.)
|
|
|
|
Arnt
|
|
|