[Tickets #11387] Re: horde_alarms tries always to login as first admin user but with an empty password

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11387
------------------------------------------------------------------------------
  Ticket             | 11387
  Updated By         | amessina at messinet.com
  Summary            | horde_alarms tries always to login as first admin user
                     | but with an empty password
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


amessina at messinet.com (2014-03-11 20:32) wrote:

>> Each time horde_alarms runs by cron, it tries to login as the first
>> admin user, but with an empty, password. So we get tons of failed
>> logins in the logs, plus this might lead to locking the account by
>> the backend.
>
> We have the same problem.  I understand the subsequent comments  
> about needing a password for IMAP.  But at least in our case, we  
> only want alarms that are stored in SQL so I'm not sure why Horde  
> needs to try (and fail) an IMAP login.
>
> A tentative solution for us is to set the 'load' parameter in the  
> 'notify' call of /usr/bin/horde-alarms to false.  This still seems  
> to email the reminders correctly, and avoids IMAP authentication  
> errors in the log.
>
> Maybe this could be made easier for users by accepting an argument  
> (e.g. '-n' for 'no load') to /usr/bin/horde-alarms, as in the  
> attached patch.

I can confirm that this solution works well for me, as I'm not using  
an IMAP backend for the calendar.  Not being intimately familiar with  
the Horde internals, I cannot comment on whether or not this is the  
*right* way to do this or not.