[CalendarServer-dev] [Calendar and Contacts Server] FAQ modified

[Calendar and Contacts Server]

Changed page "FAQ" by sagen at apple.com from 17.224.21.17*
Page URL: <http://trac.calendarserver.org/wiki/FAQ>
Diff URL: <http://trac.calendarserver.org/wiki/FAQ?action=diff&version=10>
Revision 10

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 9)
+++ FAQ (version: 10)
@@ -57,3 +57,10 @@
 {{{Mail gateway didn't find a token in message}}} -- Calendar Server uses "plus addressing" to encode a token into the reply-to address for email invitations.  That way, when a reply comes back, the token can be used to look up the appropriate organizer, attendee, and event to update.  This special tokenized email address is not only in the reply-to field, but also substituted for the organizer's email address within the embedded icalendar body attached to the invitation.  So iMIP-aware clients should direct the reply to the email address including the token.  If that token is missing, the iMIP reply is not processed.
 
 {{{iMIP injection principal not found: com.apple.calendarserver}}} -- By default, Calendar Server assumes there is a user named com.apple.calendarserver on the system and it uses that account to authenticate requests between the calendar server processes and the mail gateway process.  If you're not on an OS X server, you'll need to create a user account for this purpose, and put its username and password into the caldavd.plist as described in the steps above.
+
+
+== Configuring for LDAP ==
+
+'''How do I configure Calendar Server to use LDAP for users, groups, locations, and resources?'''
+
+See ConfiguringLDAP

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
Calendar and Contacts Server </>
HTTP/WebDAV/CalDAV Server

This is an automated message. Someone at / added your email
address to be notified of changes on FAQ. If it was not you, please
report to .