[imp] User authorization failing for imp (Horde login is ok)

[Jan Schneider]

Zitat von SSRI <ssri_abo at u-paris2.fr>:

> Jan Schneider <jan at horde.org> a écrit :
>
>> Zitat von SSRI <ssri_abo at u-paris2.fr>:
>>
>>> Jan Schneider <jan at horde.org> a écrit :
>>>
>>>> Zitat von SSRI <ssri_abo at u-paris2.fr>:
>>>>
>>>>> Jan Schneider <jan at horde.org> a écrit :
>>>>>
>>>>>>>>>
>>>>>>>>> When hordeauth is set to false :
>>>>>>>>>
>>>>>>>>> 1) Where do you configure the auth driver for IMP ?
>>>>>>>>
>>>>>>>> The only "auth driver" if you want to say so, is IMAP (or POP3)
>>>>>>>> for that matter, because those are the backends for IMP.
>>>>>>>>
>>>>>>>
>>>>>>> Ok, so no way to use an alternate backend in this case:
>>>>>>> authentication will be handled by pear/php/Horde/Auth/Imap.php
>>>>>>>
>>>>>>>>> 2) Can you choose a different auth driver from Horde ?
>>>>>>>>
>>>>>>>> Yes, but in this case you would have to login twice. That's the
>>>>>>>> use case where you WANT to set hordeauth to true.
>>>>>>>>
>>>>>>>
>>>>>>> One drawback when hordeauth is true, connexions with CalDAV clients
>>>>>>> ( horde/rpc.php/calendars/... ) always generates a login to IMP. Is
>>>>>>> there a way to disable this ? Because CalDAV clients are not
>>>>>>> supposed to use IMP and connect to the mail server.
>>>>>>
>>>>>> Of course they are, because IMAP is your authentication backend.
>>>>>>
>>>>>
>>>>> Ok. But, why, using for example LDAP auth driver for Horde,  
>>>>> Horde connects to the mail server while the CalDAV client won't  
>>>>> read any mail ?
>>>>
>>>> This is probably from the notification system checking for  
>>>> notifications on new mail. Try this:  
>>>> https://github.com/horde/horde/commit/58b39a38050571be72d8f8b8737f6dfaba49beac
>>>>
>>>
>>> We've tried this commit, but Horde still connect once to the mail  
>>> server. The only difference, there's no more the notice "HORDE  
>>> [imp] Login success for ..."
>>
>> Does it just connect, or authenticate too? Or even sending more  
>> requests to the server?
>>
>
> Before the commit :
>
> Horde logs :
>
> 2014-12-16T13:34:00+01:00 INFO: HORDE [imp] _tryLogin   [pid 12585  
> on line 686 of "...pear/php/Horde/Imap/Client/Socket.php"]
> 2014-12-16T13:34:00+01:00 INFO: HORDE [imp] _tryLogin   [pid 12585  
> on line 686 of "...pear/php/Horde/Imap/Client/Socket.php"]
> 2014-12-16T13:34:00+01:00 NOTICE: HORDE [imp] Login success for user  
> to {imap://imapserver:993/} [pid 12585 on line 157 of  
> "...imp/lib/Auth.php"]
>
> Imap logs :
>
> Dec 16 13:34:00 imapserver imaps[7619]: login: imapserver [x.x.x.x]  
> user PLAIN+TLS User logged in
> Dec 16 13:34:00 imapserver imaps[9691]: login: imapserver [x.x.x.x]  
> user PLAIN+TLS User logged in
>
>
>
> After the commit :
>
> Horde logs :
>
> 2014-12-16T13:37:45+01:00 INFO: HORDE [imp] _tryLogin   [pid 12582  
> on line 686 of "...pear/php/Horde/Imap/Client/Socket.php"]

Use Horde::debug() there instead of Horde::log() so that you get a backtrace.

> Imap logs :
>
> Dec 16 13:37:45 imapserver imaps[7619]: login: imapserver [x.x.x.x]  
> user PLAIN+TLS User logged in
>
> -- 
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org



-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject