[horde] Horde Groupware Webmail 1.2.4, Recurring Events, and Alarm E-mail Notifications

[Beth Halsema]

We are running Horde Groupware Webmail v1.2.4 and experimenting with 
recurring events and the Alarm system.  We are using the SQL database
alarm driver.

When I create a one-time event, the alarm e-mail notification that is 
sent contains the correct date and time.  The horde_alarms table's 
corresponding alarm_params information is also correct both before and
after the alarm. 

BEFORE: alarm_start | alarm_end | alarm_methods | alarm_params | alarm_internal
-------------------------------------------------------------------------------
2009-12-04 15:11:00 | 2009-12-04 16:20:00 | a:1:{i:0;s:4:"mail";} | a:1:{s:4:"mail";a:2:{s:6:"__desc";s:0:"";s:4:"body";s:110:"We would like to remind you of this upcoming event.

Test #1

Location: Here

Date: 2009-12-04
Time: 03:20pm

";}} | NULL
-------------------------------------------------------------------------------

AFTER: alarm_start | alarm_end | alarm_methods | alarm_params | alarm_internal
-------------------------------------------------------------------------------
2009-12-04 15:11:00 | 2009-12-04 16:20:00 | a:1:{i:0;s:4:"mail";} | a:1:{s:4:"mail";a:2:{s:6:"__desc";s:0:"";s:4:"body";s:110:"We would like to remind you of this upcoming event.

Test #1

Location: Here

Date: 2009-12-04
Time: 03:20pm

";}} | a:1:{s:4:"mail";a:1:{s:4:"sent";b:1;}}
-------------------------------------------------------------------------------

Perfect.  Looks good.

However, when I create a recurring event, the horde_alarms table initially
contains the correct date and time.  When the alarm is then generated, the 
alarm_params field and the body of the alarm message are modifed to contain 
the time of the alarm, not the event.

BEFORE: alarm_start | alarm_end | alarm_methods | alarm_params | alarm_internal
-------------------------------------------------------------------------------
2009-12-04 15:13:00 | 2009-12-04 16:20:00 | a:1:{i:0;s:4:"mail";} | a:1:{s:4:"mail";a:2:{s:6:"__desc";s:0:"";s:4:"body";s:121:"We would like to remind you of this upcoming event.

Recurring Event #1

Location: Freh

Date: 2009-12-04
Time: 03:20pm

";}} | NULL
-------------------------------------------------------------------------------

AFTER: alarm_start | alarm_end | alarm_methods | alarm_params | alarm_internal
-------------------------------------------------------------------------------
2009-12-04 15:06:00 | 2009-12-04 16:20:00 | a:1:{i:0;s:4:"mail";} | a:1:{s:4:"mail";a:2:{s:6:"__desc";s:0:"";s:4:"body";s:121:"We would like to remind you of this upcoming event.

Recurring Event #1

Location: Freh

Date: 2009-12-04
Time: 03:13pm

";}} | a:1:{s:4:"mail";a:1:{s:4:"sent";b:1;}}
-------------------------------------------------------------------------------

The event time should not be 03:13pm, but instead remain 03:20pm.

I have looked through the archives and bugs, trying to find anything
that my indicate an error on my part or a known bug.  Has anyone else
seen this behavior?  And if so, any suggestions as how to correct it?

Thanks in advance,
Beth

-------------------------------------------------------------------------
Beth A. Halsema                        email:bhalsema at purdue.edu
ITaP Mailhub Administrator
OVPIT - IT Systems & Operations
401 S. Grant St.                       phone:(765)496-7456
West Lafayette, Indiana 47907-2024     fax  :(765)494-0566