Calendar: reminders are issued twice

[GoogleCodeExporter]

  Hi,

  This is just an annoyance, not a severe problem I'm describing here , nevertheless I think it deserves a place in the issues list for the Calendar project.
  I have several caldavs, one public used for Birthdays and one main used for everything else. I try and insert on the Birthdays caldav a yearly recurring all day event with e-mail notification set to 5 minutes before event starts. The reminders script cron job is set to run each 5 minutes. Most of the time, I have two e-mails for each reminder I had set for the Birthdays caldav, these e-mail notifications are sent on the same run of the reminders script as the e-mails time-stamps only differ by a tiny 2 seconds amount.

What version of the product are you using? On what operating system?
- Using non official version of the bundle (1.8++, for RC-0.6, the calendar.zip 
that corrected issue 259)
- Roundcube Webmail 0.6
- Linux, Fedora Core 14
- Davical 0.9.9.7

  Thanks in advance for your time.

Regards

Original issue reported on code.google.com by cpsoa...@gmail.com on 14 Nov 2011 at 11:51

[GoogleCodeExporter]

Which users access the Birthdays CalDAV?

Check the message source of the Reminder if it is really identical.

I guess there are reminders scheduled for another user which are sent to your 
account.

Original comment by rol...@liebl.ath.cx on 14 Nov 2011 at 3:01

[GoogleCodeExporter]

Original comment by rol...@liebl.ath.cx on 14 Nov 2011 at 3:02

• Changed state: Reproducing

[GoogleCodeExporter]

  Each user has its own Birthdays CalDAV. So, these reminders are only sent to me as I'm the only user that has Birthday CalDAV populated. As for the e-mail headers, they are almost the same and only differ in obvious headers, namely, message ids and mail relay processing timestamps.

Regards

Original comment by cpsoa...@gmail.com on 14 Nov 2011 at 3:16

[GoogleCodeExporter]

  One thing that I did not mention was that I inserted all these events using a version of calendar plugin prior to 1.8, don't know if it makes any difference in the way the auxiliary db tables are populated.

Original comment by cpsoa...@gmail.com on 14 Nov 2011 at 3:19

[GoogleCodeExporter]

Truncate events_caldav and reminders table. Login and go to calendar. Report if 
issue persists.

Original comment by rol...@liebl.ath.cx on 14 Nov 2011 at 5:06

[GoogleCodeExporter]

  OK,

  Just truncated both tables, my next event of this type is tomorrow. I'll report the results from tomorrow's experience. This may be already resolved as you suggest, that is, the problem may be related to some dangling information present on those tables, I say this because if I create a similar event now, I cannot reproduce the problem, e.g., the problem only affected events that were created somewhere in the past. Thanks much.

Original comment by cpsoa...@gmail.com on 14 Nov 2011 at 5:23

[GoogleCodeExporter]

  Hi,

  Sorry, I confused the dates:  my next event was not today but on the 16th of November (tomorrow, from now). I propose we wait one more day. Sorry for the confusion. Regards.

Original comment by cpsoa...@gmail.com on 15 Nov 2011 at 11:44

[GoogleCodeExporter]

  Hi,

  Have some outcome now. I have two whole day events for today. One of them is on the Birthdays CalDAV and another one, which I inserted yesterday, on the global CalDAV. I have one reminder instance for the Birthdays event and *two* reminder instances for the  other event. Note that the other event is not recurring. So, the problem persists even after truncating the involved tables. Note that I have a 5 minutes before reminder, maybe some time range overlap on the tests you make, I don't know, but if you by any chance have a list of event triggers to send e-mails, you could only check for duplicates on that list before inserting a new notification, don't know if that's the case though. Thanks in advance.

Original comment by cpsoa...@gmail.com on 16 Nov 2011 at 10:16

[GoogleCodeExporter]

This ticket will stay open for a while. Reminders have to be re-coded. 
Reminders table grows tremendiously if we have f.e. daily recurring events with 
an expiration date far in future.

Original comment by rol...@liebl.ath.cx on 16 Nov 2011 at 6:55

[GoogleCodeExporter]

I have re-coded this section. Hope the issue is gone. If not, please re-open 
ticket.

Original comment by rol...@liebl.ath.cx on 26 Nov 2011 at 1:19

• Changed state: Fixed