[horde] IMAP overhead?

[simon at simonandkate.net]

Quoting James MacLean <macleajb at ednet.ns.ca>> On 02/22/2013 08:10 AM,  
Jan Schneider wrote:
>>
>> Zitat von Patrick Boutilier <boutilpj at ednet.ns.ca>:
>>
>>> On 02/22/2013 05:57 AM, Jan Schneider wrote:
>>>>
>>>> Zitat von Patrick Boutilier <boutilpj at ednet.ns.ca>:
>>>>
>>>>> On 02/21/2013 08:14 PM, Michael M Slusarz wrote:
>>>>>> Quoting Patrick Boutilier <boutilpj at ednet.ns.ca>:
>>>>>>
>>>>>>> I have noticed that when IMP is configured to use hordeauth then
>>>>>>> almost every link you go to in Horde or apps like Turba makes an imap
>>>>>>> connection to the IMAP server. Horde itself is configured to use LDAP
>>>>>>> authentication.
>>>>>>>
>>>>>>> Is this by design?
>>>>>>
>>>>>> Are you talking about the basic view?  If so, the IMP folder tree needs
>>>>>> to be built on every page, which needs to poll for new mail.
>>>>>>
>>>>>> This doesn't happen in the other views.
>>>>>>
>>>>>> michael
>>>>>>
>>>>>> ___________________________________
>>>>>> Michael Slusarz [slusarz at horde.org]
>>>>>>
>>>>>
>>>>> Happens in dynamic view too. Even the initial login to Horde tries to
>>>>> login to the imap server defined in IMP.  We noticed it because we are
>>>>> testing an LDAP server for authentication and using it for Horde
>>>>> login. Our imap server is not using this LDAP server for
>>>>> authentication so the passwords can be different. We noticed that if a
>>>>> user's imap password is not the same as the LDAP password the user can
>>>>> login to Horde with the LDAP password but there is a long delay
>>>>> logging in and when clicking links. Delay is caused by failed imap
>>>>> login attempts.
>>>>
>>>> This is the checking for new mail.
>>>
>>> Right, but should Horde be checking for new mail when I go into  
>>> Turba, Nag, etc.. ?
>>
>> Yes. Users want to get notified about new messages, no matter where  
>> in the groupware they are.
>>
>>> As far as I can tell every link I click on in Horde causes an imap  
>>> connection to be made. And this only happens when hordeauth=true  
>>> is used in IMP. If hordeauth=false then the imap connections only  
>>> start when you actually go into IMP.
>>
>> Correct. Authentication is only attempted if there is a way to authenticate.
>>
>>> I have not checked to see if the same thing happens if Horde is  
>>> configured to use IMP for authentication.
>>
>> It does.
>
> Hi Folks (Jan),
>
> We also notice that just logging in causes our Gollem backend to  
> authenticate. That is, we have Gollem using hordeauth=true, but we  
> are just logging in to Horde, not in to Gollem, and it will  
> authenticate against the Gollem resource (ftp in this instance)  
> every time.
>
> Is there a way to limit this to when a user actually selects a  
> Gollem resource?
>
> This even happens to users with Active-Sync doing it's normal business.
>
> Thanks,
> JES
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
>
>>>>>>> I have noticed that when IMP is configured to use hordeauth then
>>>>>>> almost every link you go to in Horde or apps like Turba makes an imap
>>>>>>> connection to the IMAP server. Horde itself is configured to use LDAP
>>>>>>> authentication.
>>>>>>>
>>>>>>> Is this by design?
>>>>>>
>>>>>> Are you talking about the basic view?  If so, the IMP folder tree needs
>>>>>> to be built on every page, which needs to poll for new mail.
>>>>>>
>>>>>> This doesn't happen in the other views.
>>>>>>
>>>>>> michael
>>>>>>
>>>>>> ___________________________________
>>>>>> Michael Slusarz [slusarz at horde.org]
>>>>>
>>>>> Happens in dynamic view too. Even the initial login to Horde tries to
>>>>> login to the imap server defined in IMP.  We noticed it because we are
>>>>> testing an LDAP server for authentication and using it for Horde
>>>>> login. Our imap server is not using this LDAP server for
>>>>> authentication so the passwords can be different. We noticed that if a
>>>>> user's imap password is not the same as the LDAP password the user can
>>>>> login to Horde with the LDAP password but there is a long delay
>>>>> logging in and when clicking links. Delay is caused by failed imap
>>>>> login attempts.
>>>>
>>>> This is the checking for new mail.
>>>
>>> Right, but should Horde be checking for new mail when I go into  
>>> Turba, Nag, etc.. ?
>>
>> Yes. Users want to get notified about new messages, no matter where  
>> in the groupware they are.
>>
>>> As far as I can tell every link I click on in Horde causes an imap  
>>> connection to be made. And this only happens when hordeauth=true  
>>> is used in IMP. If hordeauth=false then the imap connections only  
>>> start when you actually go into IMP.
>>
>> Correct. Authentication is only attempted if there is a way to authenticate.
>>
>>> I have not checked to see if the same thing happens if Horde is  
>>> configured to use IMP for authentication.
>>
>> It does.
>
> Hi Folks (Jan),
>
> We also notice that just logging in causes our Gollem backend to  
> authenticate. That is, we have Gollem using hordeauth=true, but we  
> are just logging in to Horde, not in to Gollem, and it will  
> authenticate against the Gollem resource (ftp in this instance)  
> every time.
>
> Is there a way to limit this to when a user actually selects a  
> Gollem resource?
>
> This even happens to users with Active-Sync doing it's normal business.
>
> Thanks,
> JES
> -- 
>

I had a related issue a couple of weeks ago. Horde was taking an age  
(minutes) to do anything. I discovered that it was because my Gollem  
backend was down... I wasn't trying to use Gollem so didn't notice. So  
a connected issue to your query is that with constant auth against  
your Gollem backend you will run into problems if your FTP server goes  
down.

Simon.