A Plug-In Generated File Formats

This appendix provides the following sample LDIF and XML file formats:

• User List File Format (XML)

• Distribution List File Format (LDIF)

• Public Aliases File Format (LDIF)

• Shared Folder File Format (LDIF)

• User Profile File Format (LDIF)

• MBOX Files Format

• Foldermap Structure

User List File Format (XML)

The following is the syntax of a user list file in XML format (users.xml):

<?xml version="1.0" encoding="US-ASCII" ?>
<!ELEMENT userlist (user*)>
<!ATTLIST userlist passwordencrypted CDATA #IMPLIED >
<!ELEMENT user EMPTY>
<!ATTLIST user
  sourceimapuserid CDATA #REQUIRED
  sourcex400username CDATA #IMPLIED
  sourceimappasswd CDATA #IMPLIED
  sourceimapserver CDATA #IMPLIED
 
  targetimapuserid CDATA #IMPLIED
  targetimappasswd CDATA #IMPLIED
  targetimapserver CDATA #IMPLIED
  quota CDATA #IMPLIED >

For MBOX-based migration, only the sourceimapuserid attribute is mandatory.

For IMAP-based migration, the sourceimapuserid and sourceimappasswd attributes are mandatory. If you are migrating to a new e-mail domain, you must specify this domain name in the user list file.

The following is a sample user list file for two users:

<userlist>
  <user
    sourceimapuserid="Test1_User1"
    sourcex400username="Test1 User1/imteam,dev,idc,um"
    sourceimappasswd="welcome"
    sourceimapserver="prim1"
    targetimapuserid="Test1.User1"
    targetimappasswd="welcome1"
    targetimapserver="second1"
  />
  <user
    sourceimapuserid="Test2_User2"
    sourcex400username="Test2 User2/imteam,qa,idc,um"
    sourceimappasswd="welcome"
    sourceimapserver="prim1"
    targetimapuserid="Test2.User2"
    targetimappasswd="welcome1"
    targetimapserver="second1"
    targetdomain="domain_name"
  />
</userlist>

The values for all other attributes are provided using the migration setup wizard. For any user, if the administrator does not want to use the default values, specific values can be provided using the specified format.

Distribution List File Format (LDIF)

The distribution list file, distribution_lists.ldif, that the plug-in generates is in the following format:

dn: cn= dl1
cn:dl1
objectclass:  top
objectclass: groupofuniquenames
objectclass:  orclMailGroup
orclmgprfc822mailmember: [e-mail]
orclmgprfc822mailmember: [e-mail]
mail:[e-mail]
uniquemember: [e-mail]
uniquemember: [e-mail]
uniquemember: [e-mail]

dn: cn= dl2
cn:dl2
objectclass:  top
objectclass: groupofuniquenames
objectclass:  orclMailGroup
orclmgprfc822mailmember: [e-mail]
orclmgprfc822mailmember: [e-mail]
mail:[e-mail]
uniquemember: [e-mail]
uniquemember: [e-mail]

The mail attribute contains the fully-qualified name of the distribution list. The migration tool expects the name in the format dlname@sourcedomain.

The orclmgprfc822mailmember attribute is the fully-qualified e-mail address of a user who is a member of the distribution list. The migration tool expects the name in the format source_imap_userid@sourcedomain.

The uniquemember attribute contains the sub distribution lists of this distribution list. The migration tool expects the name in the format dlname@sourcedomain.

Public Aliases File Format (LDIF)

The public alias information file, public_aliases.ldif, that the plug-in generates is in the following format:

dn:cn=alias1
name:[e-mail]
cn:alias1
orclmailemail:[e-mail]
objectclass:top
objectclass:orclMailAlias

dn:cn=alias2
name:[e-mail]
cn:[e-mail]
orclmailemail:[e-mail]
objectclass:top
objectclass:orclMailAlias

dn:cn=alias3
name:[e-mail]
cn:alias3
orclmailemail:[e-mail]
objectclass:top
objectclass:orclMailAlias

The name attribute contains the fully-qualified name of the alias. The migration tool expects the name in the format aliasname@sourcedomain.

The orclmailemail attribute is the fully-qualified e-mail address of the user for whom this alias is created. The migration tool expects the name in the format source_imap_userid@sourcedomain.

Shared Folder File Format (LDIF)

The shared folder file, shared_folders.ldif, generated by the plug-in contains information about shared folders that are being migrated, and is in the following format:

dn: cn=/pubfol
objectclass: top
objectclass: orclMailFolder
orclmailaci: [e-mail] l r w
orclmailaci: [e-mail] l r
owner: [e-mail]
cn:/pubfol
orclIsSharedFolder: false

dn: cn=/shfol
objectclass: top
objectclass: orclMailFolder
orclmailaci: [e-mail] l r w
orclmailaci: [e-mail] l r
owner: [e-mail]
cn:/shfol
orclIsSharedFolder: true

The cn attribute contains the name of the shared folder. Oracle Collaboration Suite Email Migration Tool expects the name in the format /foldername.

The orclmailaci attribute contains ACI information. Oracle Collaboration Suite Email Migration Tool expects the user name of the ACI in the format source_imap_userid@sourcedomain.

The orclIsSharedFolder attribute has a false value if the folder is a public folder.

The orclMailStore attribute contains the distinguished name of the target mail store on which the shared folder is to be created.

The owner attribute contains the fully-qualified mail address of the owner of the shared folder. The migration tool expects the name in the format source_imap_userid@sourcedomain.

User Profile File Format (LDIF)

If your source directory information comes from a user profile file, user_profiles.ldif, instead of an LDAP directory, use the following format:

dn: cn=user_given_name,dc=acme,dc=com
cn: user_given_name
mail: [e-mail]
title:title
telephoneNumber:telephone_number
homePhone:telephone_number
sn:surname
st:state
physicalDeliveryOfficeName:physical_delivery_address_of_office
manager:user's_manager
ou:organizational_unit
o:organization
secretary:name_of_secretary
postalAddress:postal_delivery_address

The only mandatory attributes are mail and sn. Mail is expected in the format sourceuserid@sourcedomain.

MBOX Files Format

The format of the MOBOX file for e-mail messages is as follows

From "idcsurname1"
From: "idcsurname1" <"idcsurname1"@incq028b.idc.acme.com>
Subject: =? ISO-8859-1? B? SGk=? =
Date: Thu, 17 Jul 2003 12:45:01  +0000
To: idcuser1.idcpost.idcdomain
Message-ID: <3F169A4D.IDCDOMAIN.IDCPOST.100.16A7470.1.2C1C.1
Rm9yd2FyZGVkIG1lc3NhZ2UgDQo= Message body goes here

From "idcsurname1" - Start of the next message
From: "idcsurname1" <"idcsurname1"@incq028b.idc.acme.com>
Subject: =? ISO-8859-1? B? Zmlyc3QgZm9yd2FyZGUgbWVzc2E=? =
 =? ISO-8859-1? B? Z2UgRndkOiBIaQ==? =
Date: Thu, 17 Jul 2003 12:45:21  +0000
To: idcuser1.idcpost.idcdomain
Message-ID: <3F169A61.IDCDOMAIN.IDCPOST.100.16A7470.1.2C1E.1>
Rm9yfbasdbZGVkIG1lc3NhZ2UgDQo= Message body goes here

Foldermap Structure

When the e-mail messages are extracted and stored in MBOX files, there should be a mapping to find out the folder name that corresponds to each file. This information is stored in the foldermap file, which the migration tool uses to find the number and the folder name mapping. A typical foldermap file will be as follows:

• S, Mailbox, 1

• S, Documents, 2

• S, Documents/Authored, 3

• S, Documents/Default Library, 4

The foldermap file name will be of the format username@domain_foldermap.