Closed Bug 311142 Opened 20 years ago Closed 19 years ago

multiple emails sent for a single event

Categories

(Calendar :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rand49x599, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 I'm cutting and pasting an entry I submitted to the mozillazine forums, where it was suggested that I open a bug report if I couldn't find one for this issue. While bugs 217629 and 196690 look similar, I think this is a different problem (or enhancement request depending on your view): I'm not sure if this is expected behavior or not, but I couldn't find any information about it in any of the online resources I searched through for calendar. I'm using the calendar extension for Thunderbird. It seems like when an alarm goes off for an event I receive 2 or 3 emails for that event. Now, I was thinking it could be because I don't acknowledge the alarm immediately when it occurs since I'm not always in front of the computer, but like I said I couldn't find any documentation that specifies Calendar will send additional emails if you don't acknowledge an alarm within a certain time. What I would like to know is: is this a bug and I should only receive a single email per event? Is there a way to change the time between emails so I can make it something huge that I'll never hit? Or is there a way to force calendar to only send a single email no matter how long it takes me to ACK the alarm? Reproducible: Sometimes Steps to Reproduce: I think: 1.Set an event for some time in the future and specify an email to be sent. 2.Don't ACK the alarm right away and multiple mails follow. 3. Actual Results: Again, the ACKing stopping the mails is my theory, I tried testing by setting an event a minute in the future, when that event fires, I get 1 mail and ACK it right away, then no more mails. It seems the only time I get multiples is if I'm not around the computer to ACK it. Expected Results: I would expect a single mail no matter how long it takes me to ACK the alarm (or an option to only send a single mail).
This same thing happens to me too and I have not been able to track down what causes it. But I too get alarms that, when they first come up, they're duplicated, sometimes triplicated. And I get multiple e-mails as well. What's worst for me is that I use the Calendar from 3 separate machines, so I may get 2 alarms for the same event at the office. Then those events get repeated again when I get home in the evening, and if I happen to boot up my laptop as well, I get the same alarms again. Even if the time has already passed. (I don't use all three machines at the same time, so I'm never "logged in" more than once on the DAV server where my calendars reside.) I can understand a task needing to be persistent, specially if it's overdue, but on events that happen at a certain time, I don't see why the alarm still goes off several hours later just because I used a different computer to get to my calendar. And I certainly don't need more than one occurance of it, let alone 2 or 3...
I experience the same problem. When an notification pops up, I get multiple (sometimes up to 20) mail notifications related to the popup notification. It seems to stop, whenever I Snooze or acknowledge the alarm, However, I feel (but I cannot prove it) that the more often I snooze or acknowledge an alarm, the more mail notifications I get the next time it pops up. I also use Calendar from multiple PCs via WebDAV, but the problem also occurs if I exclusively use one PC at the time from creating the event to its first multiple mail notification.
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
New Sunbird versions don't have the ability to email alarms. -> Marking INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.