On Aug 14, 2008, at 4:42 AM, Paul Gamble - MWEB wrote:

Aug 14 10:14:03 withnail dovecot: imap-login: MYPROXY pid=6516,
[EMAIL PROTECTED], method=PLAIN, rsock=127.0.0.1:48157,
lsock=127.0.0.1:1143, proto=IMAP, secured proxy([EMAIL PROTECTED]):
started proxying to 127.0.0.1:143/pgamble*master:
Aug 14 10:26:02 withnail dovecot: pop3-login: MYPROXY pid=6514,
[EMAIL PROTECTED], method=PLAIN, rsock=127.0.0.1:55991,
lsock=127.0.0.1:1110, proto=POP3, secured proxy([EMAIL PROTECTED]):
started proxying to 127.0.0.1:110/pgamble*master:

This is just on a dev box, hence the odd IP's, log format, etc.

I'm using "master authentication" for the backend auth and so the the
master user and separator character are imbedded in the backend user,
i.e. "client->proxy_user", ("pgamble*master" above) and it would be
convenient to have them available separately, but I can live with it
as-is.

So...great stuff, thanks very much! What is your approach with regards
to incorporating these kinds of patches (in response to ad-hoc user
requests) into your main development tree? It would obviously be nice to
know that this will be incorporated at some point...

The URL I gave was to the main v1.1 tree. So this feature will be in v1.1.3.

Would it be
feasible to add a "config variable" for this (along the lines of %u, %p,
%s, etc, etc)?

That is getting a bit crowded already. And that's proxy-specific thing so you should then have variables for the destination host and port as well.

Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to