On Tue, Jul 04, 2006 at 04:29:24PM +0200, Roberto Polli wrote: > > (which could include > > TCPREMOTEIP); that could be a fairly major shakeup though. > shortly: > can that protocol be changed? > if so, can that protocol be changed in the way I do? > or, which is the best way to do this?
Well, clearly it can be changed, as you have demonstrated. The client and server side code both exist within courier. However, getting it changed in the mainstream codebase is a matter of persuading MrSam that it should be done. This is his project, and he's the only committer. Patches to pass the remote IP address have been submitted but rejected in the past; but maybe a more general-purpose mechanism might be considered. What I'd like to see is that you can specify in the client (e.g. pop3d) a list of environment variables to be passed across: e.g. AUTHDAEMON_PASSENV="TCPREMOTEIP,LDAP_FILTER" Then I'd like to see the four different types of authdaemon request (pre, authenticate, change password, enumerate) made into the same message format, which allows the environment variables to be passed. Perhaps this format should always include a length value so that the other side knows how many bytes to read in one go, like the existing 'AUTH' message? Or maybe it should be parsed line-by-line, like the response format? In that case, requests could be the same format as responses - e.g. _REQUEST=changepass _OLDPASS=foobar _NEWPASS=baz123 TCPREMOTEIP=127.0.0.1 . Just a thought. Regards, Brian. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
