[Tickets #11766] Re: [passwd] imp is not activated.

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11766
------------------------------------------------------------------------------
  Ticket             | 11766
  Updated By         | Ralf Lang (B1 Systems GmbH) <lang at b1-systems.de>
  Summary            | [passwd] imp is not activated.
  Queue              | Passwd
  Version            | Git develop
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Ralf Lang (B1 Systems GmbH)
------------------------------------------------------------------------------


Ralf Lang (B1 Systems GmbH) <lang at b1-systems.de> (2012-12-03 14:41) wrote:

> I compared horde "packages", versions, horde, imp, passwd  
> configuration of these both instances but I didn't found anything  
> interesting. I have no idea what could be wrong. Do you think that  
> could be done with imap server? On both sites is dovecot, maybe  
> different version. I can compare configuration, but question is-  
> isn't it too low to seek the problem there?

I have no idea why your two setups differ. I progressed in analysis though.

Any IMP action for authenticated session, even ->authenticate or  
->transparent, implies PushApp and thus ->authenticated which in turn  
triggers IMP_Auth->authenticationCallback.

That one however tries to build a whole IMP environment and reuses the  
existing ->ob (IMP_Imap) instance to detect the namespace. This is  
where it fails because of the old, unchanged credentials.

I'm preparing a patch but it looks rather ugly so far and I am not  
sure it doesn't imply performance loss.