Duplicate of bug #9733.

Aha...

You got me thinking. As per instructions here:

http://www.horde.org/apps/horde/docs/INSTALL#configuring-horde

Section 5:

Setting up alarm emails

If you want your users to be able to receive emails from the 
Horde_Alarm system, you must set up a cron entry for horde-alarms, you 
must have at least one administrator specified in the Horde 
configuration, and you must have the PHP CLI installed (a CGI binary 
is not supported - php -v will report what kind of PHP binary you have).

Running the job every 5 minutes is recommended:

# Horde Alarms
*/5 * * * * /usr/bin/horde-alarms
If not installing Horde through PEAR of if PEAR's bin_dir 
configuration doesn't point to /usr/bin/, replace 
/usr/bin/horde-alarms with the path to the horde-alarms script in your 
Horde installation.



I have this setup. Disable the Cron job and the errors stop, both the 
IMAP binds with BADLOGIN and also the Turba failed LDAP binds.

Sooooo. According to the instructions -

you must set up a cron entry for horde-alarms - DONE

you must have at least one administrator specified in the Horde 
configuration - YES

and you must have the PHP CLI installed - YES

So how can I get this working without the constant errors?

Something *is* doing these authentication requests. If you can rule 
out browsers and ActiveSync clients, you have to find *what* it is.

Every 5 minutes, at the same time as Turba does a bind without a 
password as I have logged here - http://bugs.horde.org/ticket/10144 - 
Imp tries to do an IMAP login without a password.

The Horde log gets these (two every time):

2011-05-26T16:40:07+10:00 ERR: HORDE [imp] IMAP server denied 
authentication. [pid 4479 on line 343 of 
"/var/www/horde4/imp/lib/Imap.php"]
2011-05-26T16:40:14+10:00 ERR: HORDE [imp] IMAP server denied 
authentication. [pid 4479 on line 343 of 
"/var/www/horde4/imp/lib/Imap.php"]

My IMAP server has the following matching entries:

May 26 16:40:01 server04 imap[29973]: accepted connection
May 26 16:40:01 server04 master[30004]: about to exec 
/usr/lib/cyrus-imapd/imapd
May 26 16:40:01 server04 imap[30004]: executed
May 26 16:40:01 server04 imap[29973]: mystore: starting txn 2147486191
May 26 16:40:01 server04 imap[29973]: mystore: committing txn 2147486191
May 26 16:40:01 server04 imap[29973]: starttls: TLSv1 with cipher 
AES256-SHA (256/256 bits new) no authentication
May 26 16:40:01 server04 saslauthd[1516]: do_request      : NULL 
password received
May 26 16:40:01 server04 imap[29973]: badlogin: 
server06.simonandkate.lan [192.168.1.170] plaintext simon SASL(-13): 
authentication failure: checkpass failed
May 26 16:40:04 server04 saslauthd[1516]: do_request      : NULL 
password received
May 26 16:40:04 server04 imap[29973]: badlogin: 
server06.simonandkate.lan [192.168.1.170] PLAIN [SASL(-13): 
authentication failure: Password verification failed]
May 26 16:40:08 server04 saslauthd[1516]: do_request      : NULL 
password received
May 26 16:40:08 server04 imap[29973]: badlogin: 
server06.simonandkate.lan [192.168.1.170] plaintext simon SASL(-13): 
authentication failure: checkpass failed
May 26 16:40:11 server04 saslauthd[1516]: do_request      : NULL 
password received
May 26 16:40:11 server04 imap[29973]: badlogin: 
server06.simonandkate.lan [192.168.1.170] PLAIN [SASL(-13): 
authentication failure: Password verification failed]

No client access logged in httpd at that time. ActiveSync is off.

Line 343 of Imap.php is:

             $error = new IMP_Imap_Exception($e);