[imp] pass client ip during authentication
Systeembeheer BCS
adje at bezoekerscentrumsonsbeek.nl
Thu Sep 25 10:52:31 UTC 2014
Citeren Arjen de Korte <arjen+horde at de-korte.org>:
> Citeren Systeembeheer BCS <adje at bezoekerscentrumsonsbeek.nl>:
>
>> Using imp for authentication with dovecot IMAP, working fine. But now I
>> would like to make use of dovecot's allow_nets feature to restrict
>> logins from certain ip's. To make that work, imp should pass the
>> client's ip (as seen by apache) to dovecot during authentication, but
>> instead it passes 127.0.0.1 for both lip and rip. Any way to change
>> this?
>
> No. Horde doesn't pass the connecting IP to Dovecot. This is determined
> by Dovecot itself, by looking at the local and remote IP for the socket
> that is used for communication.
Ah, thanks. Looks like I have to switch to another auth mechanism
instead to get this working.
>
>> horde log:
>> 2014-09-25T11:39:54+02:00 NOTICE: HORDE [horde] Login success for
>> test at bezoekerscentrumsonsbeek.nl [192.168.4.101] to horde. [pid 6600 on
>> line 150 of "/var/www/horde/login.php"]
>>
>> mail log:
>> Sep 25 11:39:54 BCS dovecot: imap-login: Login:
>> user=<test at bezoekerscentrumsonsbeek.nl>, method=PLAIN, rip=127.0.0.1,
>> lip=127.0.0.1, mpid=8382, TLS
>
> --
> This message was sent from a mailinglist subscription address.For
> off-list replies, you must remove the address extension.
More information about the imp
mailing list