The default postmaster created by the Messaging Server configure program cannot be modified.
If you try to modify fields in the User Properties page of the default postmaster created during the Messaging Server configuration, the change operation fails.
Note that, in this situation, the Delegated Administrator console was not used to allocate service packages to the postmaster's organization, and the postmaster user was not assigned a service package.
Workaround: Use either of the following methods to solve this issue:
In the Delegated Administrator console, allocate mail service packages to the organization; then assign a mail service package to the user.
Use the Delegated Administrator utility (the commadmin command) with the -S mail option to add mail service to the organization and the user.
When a service package has IMAPS enabled but IMAP access is disabled, the Delegated Administrator console displays it as having IMAP access disabled.
Assume there is a service package that provides access to IMAPS but not IMAP. For example:
In the Delegated Administrator console, the Service Package page shows this service package with IMAP Access disabled.
A service package that has IMAP access enabled (such as the bronze service package) is displayed with IMAP enabled.
In the Create Group wizard in the Delegated Administrator console, an incorrect message appears instead of the Back to Top message.
When you search for users in the Create Group wizard—for example, when you are adding an internal member or owner—and you move the mouse over the “Back to Top” link, the tooltip message “Jump to xxx section” appears instead of “Back to Top.”
Attributes passed with the –A option of the commadmin command are ignored if the command also calls an input file containing attributes passed with –A.
This issue occurs if you run a commadmin command such as this one:
./commadmin user create -D tla -w pass -d <domain> -F test -L User -W pass -i /tmp/comm.in -A preferredlanguage:es
And the input file, comm.in, contains attributes passed with the -A option. The result is that the -A option in the command line is ignored. In the example shown above, the preferredlanguage:es is not added.
Workaround: If any attributes are passed in the input file with the -A option, pass all values of -A in the input file. Do not also use -A in the command line.
An Organization Administrator (OA) can remove himself as an OA by modifying the organization Properties page.
If you log into the Delegated Administrator console as an OA, you can go to the organization's Properties page and remove yourself from the list of users with OA rights. No error occurs, and you can continue using the console. You should either be unable to remove yourself as an OA or be logged out as soon as you remove yourself.
An inappropriate error message is displayed when you use a domain name that conflicts with the name of a deleted domain.
This issue occurs if you create an organization with a domain name that is the same as the name of a deleted domain. (The organization name is different than the name of the deleted organization.) The following error message appears: Attribute uniqueness violated.
Workaround: Specify a new domain name.
When you add Dynamic members to a group In the Delegated Administrator console, you cannot test a manually constructed LDAP URL.
When you create a new group and add dynamic members to the group, you can either manually construct an LDAP URL or use the fields available in the drop-down menus to construct the LDAP URL. If you use the drop-down menus, you can click the Test LDAP URL button. If you manually construct the LDAP URL, this feature is disabled.
Using the browser or system controls in the Delegated Administrator console can generate unexpected results.
Workaround: Navigate only by using the built-in Delegated Administrator controls, such as the tabs, buttons, and navigation links provided on the page itself. Do not use browser or system controls, such as your browser's Back button or the Close icon on dialog windows.
An incorrect error message is displayed when you create a new user with a Login ID that is already in use.
When you create a new user with a unique email address but a login ID that is already used, the user is not created (which is the correct behavior), but the following error message is displayed: “Cannot create user — mail address already used.” The error message should say that the login ID is already used.
No indication when a User, Organization, or Group list page has finished loading.
If you click a button while a list page is loading, an error occurs.
Workaround: While the page is loading, a message asks you to wait. Do not click any buttons or links until the page is ready.
The advanced search feature does not return correct results for organizations.
This issue occurs if you perform the following steps:
Select the Advanced Search feature.
Select “Organizations” from the drop-down list.
Click the Match All or Match Any radio button.
Select an organization name from the drop-down list.
Enter valid values in the text field.
Instead of returning only the organizations that match the search criteria, Delegated Administrator displays all organizations.
Cannot modify non-ASCII groups.
If a group is created with a group name that contains non-ASCII characters, it cannot be modified with the commadmin group modify command.
For example, if a group with the non-ASCII characters XYZ is specified with the -G option in the commadmin group create command, an email address of XYZ is automatically added to the group’s LDAP entry. Since non-ASCII characters are not allowed in email addresses, modifying the group with commadmin group modify fails.
Workaround: Use the -E email option when creating a group. This option will specify the group’s email address. For example: commadmin group create -D admin -w password -d siroe.com -G XYZ -S mail -E firstname.lastname@example.org .