User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20100202 Firefox/3.5.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 using Lightning 1.0b1 Using a CalDAV calendar connected to a MailEnable (version 4.22) calendar when a new event is created with attendees email is sent to past invitations in the calendar to which a reply has already been sent Reproducible: Always Steps to Reproduce: 1. Create a new event 2. Invite Attendees 3. Press the Save/Close button 4. A requester will appear: E-Mail Notification Would you like to send out email notifications Support Outlook 2000 and Outlook 200/XP OK Cancel 5 Requester does not indicate what event it is sending email for 6 Requester appears several times each time sending to past events in the calendar which have already been replied to in addition to the event which is being created 7 If you delete the event then it only sends to the correct event Actual Results: People who have sent invitations in the past are receiving email notification for the past events over and over again each time a new event is created. Expected Results: Expect the invitations to be sent out only for the event being created and not to other events in the calendar If the requester indicated which event it is sending to then the email for previous events can be canceled and email only sent to the correct event. Although this is not ideal it will work. This happens on multiple computers all with the same version of thunderbird and lightning and also it does the same on the latest versions of thunderbird 2 with the previous version of lightning.
Please enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor (Options > Advanced > General > Config Editor) and check your error console for messages.
Joe, is this still happening with the latest MailEnable version and Lightning version? I'd appreciate if you could follow instructions from comment 1 and then reopen this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.