Closed until someone can reproduce it.

That's what I was afraid of. So it looks like the problem is specific 
to my setup.



I can't even think of where to begin to troubleshoot this. Any 
suggestions? (aside from upgrading PHP)



My server runs on CentOS 4.6 with PHP 4.3.9. Here's the relevant info:



# php -v

PHP 4.3.9 (cgi) (built: Jul 16 2008 16:44:47)

Copyright (c) 1997-2004 The PHP Group

Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies

     with eAccelerator v0.9.5.2, Copyright (c) 2004-2006 eAccelerator, 
by eAccelerator



# pear list

Installed packages, channel pear.php.net:

=========================================

Package          Version State

Archive_Tar      1.3.1   stable

Cache            1.5.4   stable

Console_Getargs  1.3.4   stable

Console_Getopt   1.2     stable

DB               1.6.2   stable

Date             1.4.7   stable

Fileinfo         1.0.4   stable

HTTP             1.2.2   stable

HTTP_Request     1.4.2   stable

Log              1.11.0  stable

Mail             1.1.3   stable

Mail_Mime        1.5.2   stable

Mail_mimeDecode  1.5.0   stable

Net_FTP          1.3.7   stable

Net_SMTP         1.2.3   stable

Net_Sieve        1.1.6   stable

Net_Socket       1.0.1   stable

Net_URL          1.0.15  stable

PEAR             1.4.9   stable

SOAP             0.11.0  beta

Services_Weather 1.4.3   stable

Structures_Graph 1.0.2   stable

XML_Parser       1.2.8   stable

XML_RPC          1.5.0   stable

XML_Serializer   0.18.0  beta

XML_Util         1.1.4   stable

idn              0.1     beta

json             1.2.1   stable



# pecl list

Installed packages, channel pecl.php.net:

=========================================

Package Version State

LZF     1.5.0   stable



# httpd -v

Server version: Apache/2.0.52

Server built:   Jan 14 2008 08:20:27



Please let me know if you see anything unusual here ...

I deleted my default_alarm preference, logged out, logged back in, and 
tested with both single and recurring events, and both of them sent me 
emails with the correct data in them.

Yet another update: recurring events are still not showing up with the 
correct date in the notification e-mails.

OK, I figured out what caused the problem: Calendar Options --> Event 
Defaults ... click "Save". I'm using MySQL as a back end, and this 
option will create a "default_alarm" entry in the "horde_prefs" table 
for the user. Without it, the date and time of the event is not 
detected properly. Once it's there, even if the value is zero 
(default), the values are determined correctly. I tested this by 
deleting the entry in the database and triggering a new notification.



So the solution for me was to create an entry in "horde_prefs" for 
each account on the server.

I'm not sure whether my previous explanation of the problem was 
sufficient since the ticket is still "awaiting feedback", so I will 
try to illustrate it through an example.



I put my friend's birthday in the calendar and set it so that I get an 
e-mail notification 3 days before the event. The reminder came right 
on time, 3 days before, at the correct time, but the body of the 
e-mail did not contain the date and time of the event (as it has 
always been in previous versions of Kronolith); instead, it contained 
the current date and time. The title, subject and location of the 
event are all fine.

I'm talking about reminders for events with alarms. Add a new event 
and set the alarm to 3 days before the event starts. Configure 
Kronolith to send e-mail reminders. The e-mails will contain the date 
when the e-mail was generated, not the actual date and time of the 
event you are reminded about ...

Are you talking about alarms, event modifications, or the daily 
agenda? There are several kind of notifications in Kronolith.

In the latest version of Kronolith, e-mail notifications for events 
set in the calendar contain the wrong date and time information. For 
example, if I set an event for August 10 and ask to be reminded 3 days 
in advance, the notification e-mail will arrive on time, but the date 
and time flags in the body of the e-mail will erroneously state that 
the event is to happen at the current date (August 7 and the time the 
e-mail was generated) instead of the actual date and time of the event.



Older versions of Kronolith worked properly; the e-mail contained the 
correct "Date" and "Time" stamps of the event, according to the "Start 
On" entry in the calendar.