Now that there's no separate packages anymore, this makes a bit more sense. Changed: Removed phing and went with a custom build script for now. 1.7.12 (2014-05-15) The zip release ships with sabre/vobject 2.1.4. Description: See Section 6.1.1. We recommend upgrading to the latest Safari, Google Chrome, or Firefox. have a peek at these guys
Discussion of this Internet-Draft is taking place on the mailing list
Fixed a privilege bug in the availability system. #697: Added a "tableName" member to the PropertyStorage PDO backend. (@Frzk). #699: PostgreSQL fix for the Locks PDO backend. (@TCKnet) Removed the simplefsserver.php Unfold all header field continuation lines; in particular, lines with terminators embedded in continued header field values (that is, CRLF sequences followed by LWS) MUST be interpreted without the CRLF. As a result, attendees rarely obtain up to date participation status of other attendees. 3. That's the next step!
Added: The contentlength for calendar objects can now be supplied by a CalDAV backend, allowing for more optimizations. Changed: Sabre_VObject_Element_* classes are now renamed to Sabre_VObject_Property. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 49 B.4. Note I am using an external IMAP/SMTP.
However, only URIs containing a "host" element can be used to extract the necessary information to locate an iSchedule Receiver. Added: Simple console script to fire up a fileserver in the current directory using PHP 5.4's built-in webserver. Fixed: Issue #422: Preconditions were not being set on PUT on non-existent files. http://krypted.com/mac-os-x/configuring-calendar-server-in-mountain-lion-server/ Note that the absoluteURI rule is defined in [RFC3986].
Fixed: Assets in the browser plugins were not being served on windows machines. 1.7.6 (2013-04-08) The zip release ships with sabre/vobject 2.0.7. Fixed: Made a bunch of properties protected, where they were private before. IS:originator-invalid: The "Originator" header in the POST request did not include a valid calendar user address for the Originator of the scheduling message. Example Scheduling Transactions . . . . . . . . . . . 43 A.1.
This was already deprecated, but has now been fully removed. http://osdir.com/ml/general/2012-08/msg20806.html iSchedule Receiver Request-URI . . . . . . . . . . . . . . 12 5. Error During Post For Mailto Imip Request Failed Fixed: Range requests now work for non-seekable streams. (Thanks Alfred Klomp). administrator XML Element Name: administrator Namespace: urn:ietf:params:xml:ns:ischedule Purpose: Provides contact information for the administrator of the iSchedule Receiver.
iSchedule Senders and Receivers MUST support this method of public key retrieval. More about the author The zip release ships with sabre/vobject 3.3.4, sabre/http 2.0.4, and sabre/event 1.0.1. 2.0.5 (2014-10-14) #514: CalDAV PDO backend didn't work when overriding the 'calendar changes' database table name. #515: 304 status For clarity, I originally signed up with the following: * Note this is NOT my real email address; it might be someones … don't write to it. Added: All VObject elements now have a reference to their parent node. 1.5.3 (2011-09-28) Fixed: Sabre_DAV_Collection was missing from the includes file.
DevDmBootstrap3 created by Danny Machal Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! DKIM defines a domain-level Daboo & Desruisseaux Expires November 3, 2013 [Page 36] Internet-Draft iSchedule May 2013 digital signature authentication framework for email, using public- key cryptography, with the domain name Fixed: Issue 95: Parsing X-LIC-LOCATION if it's available. check my blog max-date-time XML Element . . . . . . . . . . . . 35 126.96.36.199.
Description: iSchedule Receivers might restrict what form of attachments are allowed in iTIP messages that are sent to it, for performance, or security reasons. However, due to complexity of managing the authorization of such requests, this specification does not allow such scheduling messages. Added: Sharee's can now also read out the list of invites for a shared calendar.
The latter is going to be deprecated in 2.1, so this makes it slightly easier to write code that works in both branches. #497: Making sure we're initializing the sync-token field Support Apple Support Communities Shop the Apple Online Store (1-800-MY-APPLE), visit an Apple Retail Store, or find a reseller. request-status XML Element . . . . . . . . . . . . 28 188.8.131.52. I will expect the clustering phase to group close points in respective clusters.
The value of this header is maintained by the iSchedule Receiver as described in Section 184.108.40.206. Is there a refresh() method as there are for Recommenders? Fixed: DTSTART values would be incorrect when expanding events. news Fixed: DATE-TIME encoding was wrong in VObject. (we used 'DATETIME').
For example, a mailto URI with the full domain "host.calendar.example.com" would first trigger a query using the domain "host.calendar.example.com", then if that failed, the domain "calendar.example.com" would be tried, then if calendar-data-types XML Element Daboo & Desruisseaux Expires November 3, 2013 [Page 32] Internet-Draft iSchedule May 2013 Name: calendar-data-types Namespace: urn:ietf:params:xml:ns:ischedule Purpose: Identifies what formats of iCalendar data are acceptable. Please type your message and try again. But how to get it to iCal?...
They will be ignored. > Macos-x-server mailing list ([hidden email]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/macos-x-server/macosxforme%40gmail.com> > This email sent to [hidden email] _______________________________________________ Do not post admin requests There was an ugly bug as far back as 10.6 server, where the keychain-stored *SMTP* password did not get updated. Once the authenticity of the message is confirmed, the iSchedule Receiver delivers the scheduling message to the indicated recipients, collects and aggregates the delivery status for each recipient, and returns the