Import of Calendar Sends out Old Event Notices
Has anyone had this issue? I attempted to import a large .ics calendar into one of my new TB calendars, and, it appears that TB then re-sent invitations to past events attendees. I cut off the import, but only after I realized this was happening.
So, attendees from past events that were listed as participants were sent an event invite for events that were, for some, 2-3 years ago. An embarrassing situation.
Did I do anything wrong with the import process? Would there have been a way to prevent TB from doing this on a calendar import?
The .ics import came from a large file where, in this large calendar ical file, the events had been sent to me from various groups from their Outlook. It appears to me that when I imported the .ics file into my new TB calendar that TB imported the past events and then assumed that I was the organizer, and TB then mailed out invites to the list of people on the attendee list.
Alle antwurden (1)
Looking at this more closely and doing some testing, it looks like when TB Imports a calendar .ics, it will then import the meeting events, but instead of doing just a straight up "save and close" it tags the "Notify attendees" (on the bottom of the meeting event, and then does a "send and close" when it imports the event.
The fix for this should be that when TB imports any .ics, it should do the following for any events where it is an invite to a meeting:
- untag the "Notify attendees" box
- do a "save and close" on that event
This should prevent the import of any .ics files where meeting events would re-send invitations to any past events etc.
- In addition, I just notice that most of the events in the original file have the "Notify attendees" box tagged. It would seem to me that, if importing an ical .ics file, TB should automatically untag all of the "Notify attendees" during the process. This would prevent any emails being sent at all during the importing of the file.
Bewurke troch Marc Paré op