MBOX-Line: From tss at iki.fi  Sat Jun 21 00:14:45 2008
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:42 2018
Subject: [Imap-protocol] Proxy IP forwarding
In-Reply-To: <1070904325.21591212350911669.JavaMail.root@dogfood.zimbra.com>
References: <1070904325.21591212350911669.JavaMail.root@dogfood.zimbra.com>
Message-ID: <1214032485.3904.1653.camel@hurina>

On Sun, 2008-06-01 at 13:08 -0700, Dan Karp wrote:
> > The idea would be that there's a frontend IMAP proxy that looks up
> > the backend IMAP server based on the username, tells the backend
> > server the user's IP and then logs in using the provided user+password.
> 
> We currently do this with a separate nginx process.  We tell the IMAP
> server the client's actual IP by having nginx do an
> 
>    A001 ID ("X-ORIGINATING-IP" "<actual-client-IP>")
> 
> as the first command, before authenticating.

Dovecot v1.2 will also support this and some other fields:

 - x-originating-port
 - x-connected-ip
 - x-connected-port

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20080621/0d34c640/attachment.sig>
