Hi, I can confirm Problems with empty pass after upgrading :(
If you need more information or a tester contact me and I will do

Since I don't see this (and neither has anyone else), it could be 
anywhere in the login process so unfortunately for these kind of 
issues that a developer can't reproduce, you necessarily need to track 
down the issue locally for use to be able to debug further.

OK Sir,

but what i should do Now ? It worked before.
In fact, the complex structure did not make it easy to debug/follow.
Can you pls. tell me what Function/Class is the Logon process is 
calling and where this information are stored, so that i can debug it.


Thank you.

Can't reproduce.  'hordeauth' works both true/false with several 
different auth backends I have tested.

There was a regression in the Imap client library that would have 
allowed an empty string to be used as a password.  That has been 
fixed, but that isn't directly related to this ticket.

Hi,

after update via PEAR from 5.1 to latest 5.2 , IMP will not send the 
correct Password
with  'hordeauth' => 'full' in backends.php.

Tracing the Logon to IMAP backend (auth from dovecot) with AUTH PLAN 
has shown that no Password (empty) is sumbitted when User log's on to 
Horde.
My Horde Auth is normally running with SQL Authentication, fetching 
the same Data from MySql Table as Dovecote Auth does. Works perfekt on 
5.1

Changed the Horde Auth to IMAP for testting to see any difference, but 
there is no.
Try'ed it with Horde auth also on IMAP will work only when 'hordeauth' 
=> false.

  'hordeauth' => true and  'hordeauth' => 'full' will not submit any Password,
and when you try to logon to IMP it will work. On CRAM-MD5 you will 
see as logon string \0[USERNAME]\0[USERNAME]