[horde] with new 3.3.4, attempts to login to horde fail

[Robert P. J. Day]

   *sigh*.  progress seems to be slow and painful.  i have my new  
3.3.4 install that i can browse to, connected to the allegedly  
upgraded horde database, but initially, there was not a single  
username/password combination i could use that would work.  so  
question 1:  can i use mysql to check in the horde database for what  
constitutes a valid name/password to horde.

   as a quick attempt, i edited conf.php and changed the existing line to:

$conf['auth']['admins'] = array('rpjday');

to try my own account to log in.  when i tried it, the horde log file gave me:

Aug 26 14:08:12 HORDE [notice] [horde] Login success for rpjday  
[192.168.169.1] to Horde [pid 12547 on line 138 of  
"/var/www/XXXXXX/horde-3.3.4/login.php"]

which looked good, until i tail'ed /var/log/syslog and read:

Aug 26 14:14:51 main dovecot: imap-login: Login: user=<rpjday>,  
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Aug 26 14:14:51 main dovecot: IMAP(rpjday): Disconnected: Logged out

   that *seems* to be telling me that the imap-login itself is  
rejecting the login.  so this seems like not really a horde problem at  
this point, but i'm open to suggestions.  when i configured 3.3.4, i  
explicitly selected what was being used before for authentication  
(from conf.php):

$conf['auth']['params']['protocol'] = 'imap/ssl/novalidate-cert';

so can someone explain why the imap-login seems to be using TLS?  that  
doesn't seem right.  do i have to reconfigure imap to match the way i  
configured horde?

rday