Issue: Events with dates prior to the year 1601 or with visibility set to "private" could cause the calendar to not sync. Resolution: GASMO now correctly stores authentication details during the session, and retries on network errors for two minutes. Issue: Under certain scenarios, users are prompted for authentication multiple consecutive times, or when network issues occurred. Now only the affected contact will fail to sync (because Outlook doesn't support years prior to 1601). Fixed an issue where contacts with a birth year before 1601 (for example, if you use "82" instead of "1982") caused Contacts sync to fail completely.Fixed an issue that caused a profile creation to fail in some cases if the Outlook language was changed after GSSMO is installed.Improved logging of some common sync and parsing failures for easier diagnostics.Updated time zone mappings for proper synchronization of Calendar events in different time zones. (Admins: See Troubleshoot network traffic issues to see whether your firewall or proxy needs to be updated). Removed unused Email Migration API scopes from OAuth authorization.Fixed an issue where losing access to a delegated account prevented the primary account being used.Improved user notification of a disabled/suspended account.Fixed an issue where GSSMO didn't correctly ask for authorization after being de-authorized.GSSMO continued to ask for authorization. Fixed an issue where network issues caused GSSMO to lose authorization.Fixed an issue that occurred when a user attempted to rename a calendar that they no longer had write access to.Fixed an issue where limited-access shared calendars-those with Permission Settings set to See only free/busy (hide details)-didn't sync properly.Fixed an issue where the GSSMO Sync Status window wasn't visible after closing and restarting Outlook.Fixed multiple issues related to outdated Windows timezone mappings.Fixed an issue that prevented setup of a new profile being completed if an existing Outlook profile is corrupted.Fixed an issue that caused synchronization failures when an iOS sync creates a "Notes" label in Gmail which conflicts with Outlook's built-in "Notes" folder.Fixed an issue that caused unwanted labels being created in Gmail for non-email Outlook folders.Fixed an issue that caused additional plaintext conference data (automatically generated by Calendar for GSSMO) to appear stacked at the end of a calendar event HTML description in Outlook.Fixed an issue that caused a sync failure to be reported when deleting an event in Outlook that was already deleted on Google Calendar.Fixed an issue that caused the sender and recipients' full names to not be displayed on sent event invites.Fixed an issue that caused synchronization errors when forwarding an occurrence of a recurring calendar event.Fixed an issue that caused synchronization errors when forwarding a calendar event with an empty description.I have no evidence that they’re “spying” on me or anything, but I’d rather be safe than sorry. I’ve thought about signing into my google calendar in the Outlook app, but I’m kind of a privacy nut, so I’d personally rather avoid having to stress or worry about trusting my workplace not to see the events from my google calendar. I noticed that DEVONthink supports email import from the Outlook application on my iMac so it got me wondering if there was a way to send (even a read-only version) my work calendar to Fantastical using whatever sorcery DEVONthink is using to see my Outlook inbox and archive. The annoying part of it is I now need to check two calendar apps (one with my Outlook and one with my personal life and freelance work) every time I want to schedule a meeting, phone call, video shoot, etc. So, I’m forced to use Outlook, and only Outlook, to perform all my email and calendar duties. They won’t allow Fantastical, Bus圜al, or even macOS or iOS system-level accounts to access the O365 data. I’ve got an Office365 account with my day job, and they’ve locked down that account like nobody’s business. I’m fully prepared for the answer to my question to be a resounding “impossible!” but I figured it wouldn’t hurt to ask… just in case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |