CHAPTER 3

Creating Mail Users

Creating User Entries  

28  

Mail User Tasks  

34  

- Activating and Deactivating Users  

35  

- Changing a Password  

36  

- Setting the Message Autoreply  

37  

- Assigning and Modifying Services for Users  

39  

- Defining New User Aliases  

40  

- Moving a User From One Server to Another  

40  

- Activating the Forwarding Address Feature  

41  

- Setting Up Additional Delivery Files  

42  

- Setting User Quotas  

43  

- Defining New User Aliases  

40  




This section discusses creating mail user entries. Also discussed are various tasks for modifying mail user entries. For each task, the attribute will be shown, and an example LDIF record will be shown to illustrate the syntax.


Creating User Entries

FIGURE  3-1 Creating a User.

E-mail users are represented in the ou=people container of the DIT. Information about users are defined in a set of attributes in an LDIF record within that container. And example is shown below.

CODE  EXAMPLE  3-1 LDIF Record for Creating a User. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


User Attributes

dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
  The distinguished name of the user Otis Fanning.

objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
  These are the object classes required in the LDAP directory entries for all users who will receive, send, or read internet email. inetOrgPerson is the structural object class.
  inetOrgPerson inherits from organizationalPerson and person. It provides attributes for describing a person belonging to an organization and who interacts with the internet.
  inetSubscriber object class provides information needed to manage a subscriber of one or more internet services (for example, sending of email, retrieving received email, calendar access, etc.).
  inetMailRouting object class contains the attributes necessary for an MTA to make routing decisions for message recipients. (A distinction is being drawn between an MTA that relays the message and the MTA that is responsible for delivering the message in a users mailbox.) This class is required for entries describing either email users (inetMailUser) or email groups (inetMailGroup).
  inetMailUser object class specifies attributes used to store and retrieve information related to storage of incoming email and sending of outbound email.

inetOrgPerson Attributes

cn: Otis Fanning
  cn (commonname) is the user's full name and is inherited from the person object class. The cn attribute is required to be unique within a domain, however, the same cn can exist in a different domain.
 
sn: Fanning
  sn (surname) is the user's last or family name and is inherited from the person object class.
 
initials: OTF
  initials contains the initials of some or all of an individuals names. In this example OTF stands for Otis Tiberus Fanning.
 
givenName: Otis
  givenName is the first name of the user.

mail: otis.fanning@stream.com
  mail The user's advertised e-mail address (RFC 822 format).
 
uid: fanning
  uid is the subscriber's login id used to log in to a computer system. This attribute must be unique within the naming context associated with containing DNS domain.
 
userPassword: {sunds}...
  userPassword is the encrypted string representing the user's password and is inherited from the person object class.

inetSubscriber Attributes


Note - uid is an attribute for both inetOrgPerson and inetSubscriber. The attribute is exactly the same.
 
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
  inetAuthorizedServices indicates the list of internet services which the user is authorized to access within the domain. If this attribute is not set, then the user has permission to use all supported services, but still subject to service permitted for the domain.

Note - We recommend adding a directory access control rule to the system to restrict the user's ability to modify this attribute. Refer to the directory service documentation for details on how to do this.
inetSubscriberStatus: active
  This attribute specifies the global access status of the user's account. The intent of this attribute is to allow the ISP to suspend and reactivate the user's account. The values are:

active - the user's account is active and the user may use all accesses granted by inetAuthorizedServices.

inactive - the user's account is inactive and the user may not use any services granted by inetAuthorizedServices. Service requests for a user marked as inactive must return transient failures. This will allow sending MTAs to retry message delivery for suspended users.

deleted - the user's account is marked for deletion. The account may remain as marked for deletion within the directory for a period of time, unless there is a purge operation for deleted users. Service requests for a deleted user are returned as permanent failures.


inetMailRouting Attributes

mail: otis.fanning@stream.com
  mail is the user's advertised e-mail address (RFC 822 format).

Note - mail is an attribute for both inetMailRouting and inetOrgPerson. The attribute is exactly the same.
 
mailHost: route66.stream.com
  mailHost is a fully-qualified hostname of the mail server where the user's Inbox is located.
 
rfc822MailAlias: ofanning@stream.com
  rfc822MailAlias stores alternate e-mail addresses for the user. Mail to any of the rfc822MailAlias will be delivered to the user associated with that entry. The value in this attribute must be unique for all mail and rfc822MailAlias attributes in a domain.

inetMailUser Attributes

inetMailUserVersion: 1.0
  inetMailUserVersion indicates the version tag of this object class. This allows LDAP clients supporting internet e-mail services to retrieve LDAP objects supporting a particular version of schema. The starting value for a version tag is 1.0. Changes to this object class must also increment the value in the inetMailUserVersion attribute.

dataSource: @(#)mkdirdata.sh 1.10 02/19/99
  dataSource is a free form text string that describes the source or identifier of the provisioning tool.

mailDeliveryOption: mailbox
  This attribute specifies one or more delivery options for inbound messages to a designated recipient. The inbound messages can be delivered into multiple message stores, however, the message access server can read messages from only one message store. This message store is specified by the mailFolderMap attribute. The IMTA reads mailDeliveryOption to determine message delivery for all messages inbound to a particular user. The values for this attribute can be:
  mailbox - Deliver mail to a vendor specific/high performance Message Store mailbox. The mailFolderMap attribute specifies the mail store from which a Message Access agent would expect to retrieve delivered mail. For example, in SIMS, provisioning a user to read messages from the Sun Message Store requires setting the mailDeliveryOption to mailbox, and the associated mailFolderMap attribute to Sun-MS. (Please refer to the description of the mailFolderMap attribute below.)
  native - this option applies only to the inetMailUser object class. It specifies delivery of mail to a local sendmail-style file system mailbox (also known as the
/var/mail box). If mailDeliveryOption is set to native, then the mailFolderMap attribute must be set to UNIX V7 in order for the user to read messages from the /var/mail using the Sun internet email product's message access services. Please refer to the mailFolderMap below and mailMessageStore ("Setting Up Additional Delivery Files" on page 42)attribute definitions.
  autoreply - Deliver mail to an auto-reply facility. When this value is set, the behavior of the autoreply feature of the MTA will be controlled by the following inetMailUser attributes:
  mailAutoReplyStartDate, mailAutoReplyExpirationDate, mailAutoReplyTimeout, mailAutoReplySubject, mailAutoReplyText, and mailAutoReplyTextInternal. See "Setting the Message Autoreply" on page 37.
  program - delivers mail to a program. For security reasons, the value of this attribute is restricted to authorized programs. This list is configured and maintained by the SIMS Administrator. Refer to the section on Alternative Delivery Programs in the SIMS System Administration Guide
  forward - forward mail to another RFC 822 compliant address as specified by the attribute mailForwardingAddress
  file - appends incoming mail to a file. The mailDeliveryFile attribute must point to a valid file for this option to work. Refer to the schema chapter in the SIMS Reference Manual.

mailFolderMap: Sun-MS
  mailFolderMap is the message store for a user's mail folders. Message access servers (IMAP server, POP server, etc.) use this attribute to determine a user's primary mailbox. An IMTA may deliver a message into multiple locations, and message access servers have to be told the default mailbox of the user. Supported values in the unbundled Sun internet email product are:

UNIX V7 - sendmail-style message store

Sun-MS - Sun Message Store, which is accessed through IMAP or POP protocols

mailQuota: -1
  This indicates the maximum size (in bytes) of the user's message store, including the Inbox and any other mailboxes. The values can be -1 or -2 or a specific storage size. A value of -1 denotes no limit on the size of messages in the user's Inbox and folders. A value of -2 sets the mail quota to the system default as specified in the message stores configuration file (see the ims.cnf man page).
  The default unit can be overridden by using one of the following tags:

<size>K - size is specified in kilobytes

<size>M - size is specified in megabytes

<size>G - size is specified in gigabytes

<size>T - size is specified in terabytes


Mail User Tasks

Activating and Deactivating Users  

35  

Changing a Password  

36  

Setting the Message Autoreply  

37  

Assigning and Modifying Services for Users  

39  

Defining New User Aliases  

40  

Moving a User From One Server to Another  

40  

Activating the Forwarding Address Feature  

41  

Setting Up Additional Delivery Files  

42  

Setting User Quotas  

43  

This section describes how to implement common tasks on user entries. The entire LDIF record is given for each task, however, most tasks require only adding or modifying one or more attributes to an existing user. Instead of using the entire record, use only the lines in italics. For example, to do the task described in the following section using ldapmodify, you would do:

# ./ldapmodify -D "<SIMS Admin DN>" -w <passwd> -f change.ldif

where the contents of change.ldif is:

dn: cn=Eileen Fanning,ou=People,dc=stream,dc=com,o=internet
changetype: modify
add: inetSubscriberStatus
inetSubscriberStatus: active


Activating and Deactivating Users

To activate or deactivate a user in the hosted domain, you must define the inetSubscriberStatus attribute in the user's entry. This attribute specifies the status of the user's account. The values are:

active - the subscriber account is active and the subscriber may use all accesses granted by inetAuthorizedServices.
inactive - the subscriber account is inactive. The subscriber may not use any services granted by inetAuthorizedServices. An inactive account may be activated by setting the attribute to active. Service requests for an inactive user are returned as transient failures.
deleted - the subscriber account is marked for deletion. The account may remain as marked for deletion within the directory for a period of time, unless there is a purge operation for deleted users. Service requests for a deleted user are returned as permanent failures.

An example of an LDIF entry that changes the user's subscriber status follows:

CODE  EXAMPLE  3-2 LDIF Record for a User's Subscriber Status. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: inactive
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Changing a Password

You can change the user's password in the LDIF record by changing the userPassword attribute.


Note - You cannot change the password of the SIMS "super" Administrator (that is, the password of the SIMS Administrator as defined by the adminBindDN attribute in the /etc/opt/SUNWmail/sims.cnf file) using the LDAP commands.

CODE  EXAMPLE  3-3 LDIF Record for Changing a User's Password. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: 2bornot2b
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: inactive
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1



Setting the Message Autoreply

You can configure the SIMS server to produce an automatic reply to any incoming email to a user's account. This is handy for when the user goes on vacation or is away from his system for a period of time. The required attributes are part of the inetMailUser object class and consist of the following: mailAutoReplyStartDate, mailAutoReplyExpirationDate, mailDeliveryOption, mailAutoReplySubject, and mailAutoReplyTextInternal.

The mailDeliveryOption attribute activates the autoreply feature when it is set to autoreply.

mailAutoReplyStartDate specifies when the IMTA should enable the automatic replies to incoming mail for the user. The format for setting this attribute is the 4-digit year, 2-digit month, and 2-digit day, 2-digit hour, 2-digit minute, 2-digit second and terminating with a Z for Zulu time. For example to set it to start at 4PM on June 21, 1999, the value of start date is 19990622000000Z

mailAutoReplyExpirationDate specifies when the IMTA should disable the automatic replies to incoming mail for the user. The format for setting this attribute is the same as mailAutoReplyStartDate.

mailAutoReplyTimeout defines the duration (in hours) between successive auto-replies to the incoming message from a specific sender. If you do not specify a timeout in the LDIF record, the timeout will be automatically set for seven days. This is used so that a sender doesn't get an autoreply for every email they send. They will only get the autoreply message as often as specified in this attribute.

mailAutoReplySubject specifies the subject line of the autoreply message. If the attribute specification contains the token $SUBJECT, then the token is replaced by the subject line of the inbound message.

mailAutoReplyText defines the body text of the autoreply message. If the attribute contains $SUBJECT or $BODY in the LDIF entry, these tokens are replaced by the subject or body of the inbound message. Use $ as a line separator.

mailAutoReplyTextInternal defines the body of autoreply messages for internal auto-replies. Senders within the same domain will receive this message. If the attribute contains $SUBJECT or $BODY in the LDIF entry, these tokens are replaced by the subject or body of the inbound message. Use $ as a line separator.

An example of the LDIF entry to enable the message autoreply for a users is below. Note that the mailAutoReplyText attribute-value pair spans several lines and that each line after the first must start with a blank space. (If you are reading this on-line, this space may not be displayed in your browser.)

CODE  EXAMPLE  3-4 LDIF Record for Activating a User's Autoreply Feature. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: autoreply
mailAutoReplyStartDate: 19990622000000Z
mailAutoReplyExpirationDate: 19990629000000Z
mailAutoReplyTimeout: 6
mailAutoReplySubject: Otis is on vacation
mailAutoReplyText: Otis is out on vacation and will return
1/2/2000. $ If you need immediate assistance on $SUBJECT than
please contact Mike Marola at marola@marola.com.
mailAutoReplyTextInternal: Otis out until 1/2/2000.
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Assigning and Modifying Services for Users

Assign and modify services for users by adding or removing service arguments to the value of the inetAuthorizedServices attribute.

CODE  EXAMPLE  3-5 LDIF Record for Changing a User's Services. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Defining New User Aliases

You can assign additional values for the rfc822MailAlias to define aliases for a user. The new values must be unique for both users and groups in the domain namespace.

CODE  EXAMPLE  3-6 LDIF Record for Defining New User Aliases. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
rfc822MailAlias: Otis.Fanning@us.stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: Otis.Fanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Moving a User From One Server to Another

You can change the user's mail storage server by changing the server assigned to the mailHost attribute.



CODE  EXAMPLE  3-7 LDIF Record for Moving a User from One Server to Another. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: antelope.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Activating the Forwarding Address Feature

Set the mailDeliveryOption attribute to forward to activate the forwarding feature. Set the forwarding address by assigning a valid email address to the mailForwardingAddress attribute. If the user wishes to continue receiving mail on his default server and also forward the mail, then set the mailDeliveryOption attribute to mailbox as well as forward. The example below demonstrates this.

CODE  EXAMPLE  3-8 LDIF Record for Activating Forwarding Addressing. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: forward
mailDeliveryOption: mailbox
mailForwardingAddress: Otis.Fanning@hawaiian-beach.com
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Setting Up Additional Delivery Files

You can set up the system such that a user's messages are sent to either a specified file (use the mailDeliveryFile attribute) or to a local sendmail-style file system mailbox (use the mailMessageStore attribute).

mailDeliveryFile is the fully qualified pathname of a file to which incoming messages are appended. This file must be accessible for writing from the file system on the user's mail host.

mailMessageStore is the file system location for a user's Inbox. This attribute only takes effect when a mailDeliveryOption is set to native (see "mailDeliveryOption: mailbox" on page 32). The IMTA will deliver incoming messages to this file. The filesystem location is in the context of the mail host. If this value is missing and the user's mailDeliveryOption is set to native, then a default of /var/mail is used by the server. This attribute specifies only the name of the directory; to derive the full name of the Inbox, the value of the uid attribute (see "uid: fanning" on page 30) is appended to the directory name.

The file below creates a user whose mail is delivered to /var/mail/fanning and to /home/fanning/Maibox.

CODE  EXAMPLE  3-9 LDIF Record for Setting Up Delivery Files. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryFile: /home/fanning/Mailbox
mailMessageStore: /var/mail/
mailDeliveryOption: native
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: -1


Setting User Quotas

  A user quota is the amount of space allocated to a user for his mailboxes. Set user quotas by specifying the value of the mailQuota attribute to the maximum size (in bytes) of a user's message store. Note that this includes the Inbox and all other mailboxes or folders which the user may have in the message store. A value of -1 or a missing value denotes no limit on the cumulative size of messages in a user's Inbox and/or folder collection. A value of -2 implies that the system or domain default is used. The default unit of bytes may be overridden by using one of the tags listed below prefixed by the size:

<size>K - size is specified in kilobytes

<size>M - size is specified in megabytes

<size>G - size is specified in gigabytes

<size>T - size is specified in terabytes

CODE  EXAMPLE  3-10 LDIF Record for Setting a User Quota. 
dn: cn=Otis Fanning,ou=People,dc=stream,dc=com,o=internet
objectClass: inetOrgPerson
objectClass: inetSubscriber
objectClass: inetMailRouting
objectClass: inetMailUser
cn: Otis Fanning
sn: Fanning
initials: OTF
givenName: Otis
mail: Otis.Fanning@stream.com
uid: fanning
userPassword: secret
inetAuthorizedServices: imap
inetAuthorizedServices: pop3
inetAuthorizedServices: imaps
inetAuthorizedServices: pop3s
inetAuthorizedServices: sunw_webaccess
inetAuthorizedServices: sunw_calendar
inetMailUserVersion: 1.0
inetSubscriberStatus: active
rfc822MailAlias: ofanning@stream.com
mailDeliveryOption: mailbox
mailHost: route66.stream.com
mailFolderMap: Sun-MS
dataSource: @(#)mkdirdata.sh 1.10 02/19/99
mailQuota: 9M




Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.