Here is the relevant extract from the log for a single calendar item, which sets an alarm every time. Is that sufficient? [calAlarmService] considering alarm for item: Office accommodation discussion alarm time: 2011/06/20 12:45:00 UTC isDate=0 snooze time: 2011/06/20 12:45:00 UTC isDate=0 [calAlarmService] now is 2011/07/02 12:49:32 UTC isDate=0 [calAlarmService] last ack was: 2011/06/20 12:44:59 UTC isDate=0 [calAlarmService] alarm is in the past and unack'd, firing now! Office accommodation discussion When: 20 June 2011 14:00-14:30 (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London. Where: R3, 2.30 Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* 2011-06-17T07:44:19Z 2011-06-20T13:00:00Z true 1525252321 2011-06-20T13:00:00Z BAAAAIIA4AB0xbcQGoLgCAAAAADgXNa9yizMAQAAAAAAAAAAEAAAAJVnvBLmO2tAvnnO05rhRy8= 040000008200E00074C5B7101A82E00800000000E05CD6BDCA2CCC010000000000000000100000009567BC12E63B6B40BE79CED39AE1472F 2011-06-20T13:00:00Z 2011-06-20T13:30:00Z false R3, 2.30 false Single NoResponseReceived ZZZZ xxx@yyyy SMTP ZZZZ xxxx@yyyy SMTP Unknown ZYZYZY xxxx@yyyy SMTP Unknown d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: getItemReply d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: modifyItem d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: PS: NEEDS-ACTION [calAlarmService] considering alarm for item: Office accommodation discussion alarm time: 2011/06/20 12:45:00 UTC isDate=0 snooze time: null [calAlarmService] now is 2011/07/02 12:50:14 UTC isDate=0 [calAlarmService] last ack was: 2011/07/02 12:50:13 UTC isDate=0 [calAlarmService] Office accommodation discussion - alarm previously ackd. d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: modifyItem d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: PS: NEEDS-ACTION