In Axigen no other local calendar folders implement FreeBusy.
EM CLIENT SYNC ERROR UPDATE
Only events from the Calendar folder are taken into account when computing FreeBusy. Had a crunch project for a client and Adobe XD wouldnt update (which I needed to update in order to access the shared cloud document). The calendar API detects a change in the calendar object (an attendee has been removed) and sends a cancellation message to that attendee (in our case the organizer).Īxigen does not send attendee notifications for local folders that are not the default folder (Calendar)Īxigen current implementation - present in WebMail too. When WebMail edits the VCALENDAR it removes the ATTENDEE property above. Calendar.app) editing the event via WebMail causes the event to be canceled.Ĭalendar.app adds an ATTENDEE property for the organizer in the VCALENDAR. When an Axigen user is organizer in an event and the event is created by a CalDAV client (e.g. WebMail and Outlook however, display events only for those days that match the repeating rule. It interprets the DTSTART as the first occurrence of the event, event if it does not match the date when the event repeats itself. The Axigen Calendar API is unable to parse the RRULE created by Calendar.app.Ĭalendar.app ↔︎ WebMail / Outlook connector interoperability issueĬalendar.app has a different interpretation to RRULEs when interpreting yearly recurrent events. Notifications belonging to events accepted from Axigen WebMail remain in the Calendar.app INBOX.Īt this point we have not found a way to tell Calendar.app to dismiss a notification that has already been processed outside the Calendar.app (in our case in WebMail).Ĭalendar.app cannot create events with custom monthly rules (repeats monthly on the 12th, 14th, and 26th). If Axigen would implement schedule status values the CalDAV client would be informed of a delivery failure in the VCALENDAR item. Based on our eM Client review, this email software doesn’t only help you manage your email accounts it has a calendar, tasks, in-built contacts, and you can use it to monitor social media interactions with your contacts.
EM CLIENT SYNC ERROR MAC OS
If the organizer makes a mistake when filling in the address of the attendee in the current implementation he/she can notice this mistake when he/she receives the NDR (non delivery report) for the iTIP message. The eM Client is one such email client that people can use on Windows, Linux, and Mac OS X.
RFC 6638 describes a mechanism that allows a CalDAV client to know the status of the iTIP delivery for a given attendee.Į.g. This is a set of issues that are indirectly related to CalDAV they are interoperability issues that manifest in CalDAV but their root cause is in Axigen's implementation.Īxigen does not implement support for schedule status values