Specifying the Required LDAP mail Attribute

Calendar Server 6 2004Q2 was the first release to require users to have the LDAP mail attribute for both user calendars and resource calendars.

For clients to use Microsoft Outlook to schedule resource calendars (for example, for meeting rooms or equipment such as a notebook computer or overhead projector), each resource must have an email address, even though email is not actually needed. The LDAP mail attribute specifies this email address.

You can add the LDAP mail attribute as follows:

• Calendar Server 5 Installation. Before you run the cs5migrate migration utility, add the mail attribute to users for user calendars. To add the mail attribute, use the Calendar Server csattribute utility or a utility such as the Directory Server ldapmodify utility.

  ---

  Note –

  If you are migrating from Calendar Server 5 to the latest version of Calendar Server, you must run the cs5migrate command with the -r option to convert the database in order to comply with the Connector for Microsoft Outlook data model. Consult technical support for information about the cs5migrate utility.

  ---

• New Installation (beginning with Calendar Server 6 2004Q2 ). Provision the LDAP mail attribute for existing users for both user and resource calendars with the Calendar Server csattribute utility or a utility such as the Directory Server ldapmodify utility.

If you are using Schema 1 and are creating new users or resources after installation, use the following utilities to specify an email address:

• For new resources:csresource -m

• For new users: csuser -m utility for new users

For related information about csattribute, csresource , and csuser, refer to theSun Java System Calendar Server 6 2005Q4 Administration Guide. For related information about the ldapmodify utility, refer to the Sun Java System Directory Server Resource Kit Tools Reference.

For Schema 2, Communications Services Delegated Administrator is the preferred tool for creating new users and resources after installation. See the Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide for information about using Delegated Administrator.

Adding the LDAP email Attribute to a Resource

The following example adds the LDAP mail attribute for a conference room named Room100 on the sesta.com server. This example configures Messaging Server. If you are using another email server, refer to that product’s documentation for the equivalent process.

1. Add the mail attribute to the LDAP server using the csattribute utility:

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

2. To check that the attribute has been set, use the csattribute list command with the -v (verbose) option:

   ./csattribute -v list Room100 ... cn=Room 100,ou=conferenceRooms,dc=sesta,dc=com has mail: Room100@sesta.com

Setting the bitbucket Channel for Resource Email (Messaging Server)

The following example sets up the bitbucket channel for Messaging Server for the email generated for resource calendars. This example uses a resource named Room100 on the sesta.com server. If you don’t set up the bitbucket channel (or equivalent), you will need to periodically delete the email messages sent to the resource calendar.

1. Ensure the bitbucket channel is defined in the Messaging Server's MTA configuration file (imta.cnf).

2. To direct messages to the bitbucket channel, create the email address for the resource using the csresource utility:

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

   ---

   Note –

   To enable these changes, you might need to rebuild alias tables or configurations. Refer to the documentation for Messaging Server (or your email product) as well as your site's documentation and procedures regarding changes to mail services.

   ---

Setting the bitbucket Channel for Resource Email (Sendmail)

The following example sets up the bitbucket channel for Sendmail for the email generated for resource calendars. This example uses a resource named Room100 on the sesta.com server. If you don’t set up the bitbucket channel (or equivalent), you will need to periodically delete the email messages sent to the resource calendar.

1. In the /etc/aliases file on the appropriate host, add an entry such as:

   # Resource/Conference room aliases Room100: /dev/null

2. Add the email address for the resource to the LDAP directory using the csresource utility:

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