14.4 Adding the mail Attribute to User, Group and Resource LDAP Entries

This section contains conceptual information and instructions for enabling LDAP entries for mail service.

This section covers the following topics:

• 14.4.1 Overview of Adding Mail Service to Calendar Server LDAP entries

• 14.4.2 To Check if the mail Attribute Exists in the LDAP Entry

• 14.4.3 To Add the Mail Attribute to Existing User, Group and Resource LDAP Entries for Calendar Server Version 6.3

14.4.1 Overview of Adding Mail Service to Calendar Server LDAP entries

Calendar Server requires users, groups and resources to have the mail attribute, which contains the email address of the user, group or resource. This enables people to search for calendars using either an email address or a calid. When you create new users with Delegated Administrator, it adds the mail attribute automatically. This happens even if the user has not been assigned mail service. However, if your users and resources were created in a version of Calendar Server when the mail attribute was not required, you might have to add the mail attribute to your existing user and resource LDAP entries.

Adding the mail attribute does not enable email notifications for user calendars.

Calendar Server does not support email notifications for group, or resource calendars.

To enable email notification for user calendars, add the following two attributes to the user’s LDAP entry:

• icsExtendedUserPrefs:ceNotifyEnable=1

• icsExtendedUserPrefs:ceNotifyEmail=jdoe@sesta.com

14.4.2 To Check if the mail Attribute Exists in the LDAP Entry

If you do not know if your users, groups and resources have the mail attribute, for Schema version 2 environments, use Delegated Administrator to check for mail services.

For Schema version 1 environments, use the csattribute list command with the -v (verbose) option.

For example, to check if the conference room resource Room100 has the mail attribute, you would issue the following command:

csattribute -v list Room100

The output tells if the mail attribute is present:

cn=Room 100,ou=conferenceRooms,dc=sesta,dc=com
 has mail: Room100@sesta.com

If the mailattribute exists, you do not have to add it. If the attribute does not exist, then add it as shown in the section that follows.

14.4.3 To Add the Mail Attribute to Existing User, Group and Resource LDAP Entries for Calendar Server Version 6.3

If you are converting existing LDAP entries to calendar enabled entries, you must add the mail attribute to each user, group and resource LDAP entry that does not contain it.

To add the mail attribute to existing users, groups and resources, use one of the following methods:

• Use Delegated Administrator Utility for a Schema version 2 Environment.

  Use the commadmin user|resource|group modify -A option.

  For example: commadmin group modify -A +mail:jdoe@sesta.com

• Use the Calendar Server D.3 csattribute utility for a Schema version 1 environment.

  The following example adds the LDAP mail attribute for an existing conference room named Room100 on the sesta.com server:

  csattribute -a mail=Room100@sesta.com add Room100

• Use ldapmodify to add the attribute directly to the LDAP entries for either Schema version.