MBOX-Line: From robsiemb at google.com  Mon Jun 23 08:59:47 2008
To: imap-protocol@u.washington.edu
From: Rob Siemborski <robsiemb@google.com>
Date: Fri Jun  8 12:34:42 2018
Subject: [Imap-protocol] Proxy IP forwarding
In-Reply-To: <1212348043.3904.521.camel@hurina>
References: <1212341451.3904.500.camel@hurina>
	<0i/azqanypELGcsgZG99yw.md5@lochnagar.oryx.com>
	<1212348043.3904.521.camel@hurina>
Message-ID: <5b93232d0806230859i38008718sc2934fa228035cc9@mail.gmail.com>

On Sun, Jun 1, 2008 at 12:20 PM, Timo Sirainen <tss@iki.fi> wrote:

> On Sun, 2008-06-01 at 20:45 +0200, Arnt Gulbrandsen wrote:
> > 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?
>
> No, not what I meant.
>
> > Cyrus Murder?
>
> Maybe. I tried to look into the Cyrus code but I couldn't find what
> commands it uses.


Its been a while but as far as I remember the murder code just uses normal
IMAP all the way (to do the proxy auth, it uses a SASL mech that supports
it), but the IP is not passed.

-Rob

-- 
Rob Siemborski | PGP:0x5CE32FCC | robsiemb@google.com
Software Engineer | | 650-623-6925
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080623/c2282e47/attachment.html>
