22 Sep
2007
22 Sep
'07
6:25 p.m.
On Sun, 2007-09-09 at 13:26 +0100, Ed W wrote:
Any suggestions on how this could be done more dynamically, or else could I raise a feature request that the auth process somehow realises when it's being forwarded to an IP address that it's actually listening on already already (ie it's a request which loops back to itself), thus simplifying the config files? I haven't cracked open the code, but it sounds somewhat possible to check the list of IP addresses we are currently listening on and check that the proxy dest isn't among them?
Try the attached patch. It probably causes the login to fail then. If it works, I'll continue with a dovecot-auth patch that does the same thing to make it really work automatically.