Oracle Email Administrator's Guide Release 9.0.3 Part Number B10033-01 |
|
| View PDF |
This chapter discuses how to administer Oracle Email.
This chapter contains the following topics:
To perform initial administration tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine
name>:<port
number>/um/admin/UMAdminLogin.uix
Once administrators have logged in, they can perform the following tasks:
After performing initial administration tasks, Oracle Corporation disabling the initial administration pages to avoid inadvertent changes to the system.
Note: This task is to be performed only if domain creation failed during the configuration of Oracle Email. |
Perform the following steps to create the initial domain:
UMADMIN
password. This is the password designated during configuration.Perform the following steps to create the initial user:
Perform the following steps to change the administrator password:
Using the Thin Client, administrators can perform domain, user, list, and alias management tasks by clicking on the appropriate tab.
Under the Overview tab, you can view what components are installed on the different middle tier hosts. To administer these components, click on the host links and you will be redirected to the Oracle Enterprise Manager.
To perform administration tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
Using the Thin Client, administrators can perform domain management tasks, such as create domains, modify domain settings for users, and modify domain settings for lists.
To perform administration tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
Perform the following steps to create domains:
Perform the following steps to modify domain preferences for users:
The following is a list of user domain parameters:
Note: These parameter is present at the domain level preferences for users. The values set here are inherited by all new users in the domain during user creation time. |
This parameter stores the DN of the mail store the user belongs to. The mail store for a user is the database that contains mail user information.
This parameter stores the e-mail quota of a mail user in megabytes. This parameter is present at the domain level preferences for users.
This parameter stores the quota for the voice mail user in megabytes. This parameter is present at the domain level preferences for users.
This parameter displays the number of message headers displayed on a single page of the Thin Client.
This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis.
This parameter specifies the domains a user can access.
This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis. This parameter enables binary attachment search for users
This is an end user parameter that enables account access from outside a firewall. This preference is only used when the client has been configured to check for this preference before enabling users to connect. Typically, the WebMail client is configured in this manner when it is facing outside the firewall. This configuration can be used in conjunction with another WebMail client that is inside the firewall and not configured to check for this preference so that a user can log in from within the firewall, enable, or disable the preference, and then subsequently log in or prevent log in from outside the firewall. For security purposes, this preference is set to disabled by default.
This is an end user parameter that specifies whether the message view display should occur in a new browser window. When disabled, the application displays message views in the same window.
This is an end user parameter that specifies whether a message view displays all the headers that a message contains. If disabled, only the common headers are shown. The commom headers are:
Perform the following steps to modify domain preferences for lists:
The following is a list of parameters for list domains:
This parameter indicates the maximum size (in bytes) of a message delivered to the list. Any message larger than this size is rejected.
This parameter is the mail ID to which all commands to the list should be sent. The default is <listname>-admin@domain
.
This parameter specifies the type of the list. Possible values are announcement, discussion, edited, or moderated.
This parameter denotes the type of subscription control on this list. Valid values are open, restricted, or closed.
This parameter is a single line phrase describing the topic of discussions on this list.
This parameter is a multi-line field that owners can use to include descriptive text about the list.
This parameter is set to true if the owner wants all subscription requests to be reconfirmed with the user.
This parameter is a multi-line text sent in e-mail to users invited by a list owner to join their list.
This parameter is defines the level of control a list owner wants on who can post messages to their list. Valid values are open or subscriber.
This parameter contains the list of users (mail IDs) who are the editors of the list.
This parameter contains the list of users (mail IDs) who are the moderators of the list.
This parameter enables a list owner to support mail merge or scheduled mail delivery, this attribute contains the tag that is used for specifying mail merge and scheduler tags.
Using the Thin Client, administrators can perform user management tasks, such as add, remove, and modify e-mail users.
To perform administration tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
Through the Oracle Email Overview page, you can view what components are installed on the different middle tier hosts. To administer these components, click on the host links and you will be redirected to the Oracle Enterprise Manager.
Perform the following steps to add e-mail users:
Perform the following steps to modify e-mail user parameters:
The following is a list of e-mail user parameters:
This parameter specifies the user ID.
This parameter stores the DN of the mail store the user belongs to. The mail store for a user is the database that contains mail user information.
This parameter stores the e-mail quota of a mail user in megabytes.
This parameter stores the additional quota for the voice mail user
This parameter defines if the user is active or inactive. If the parameter is set to active, the user will be able to receive and send e-mail. If the parameter is set to inactive, the user will not be able to receive and send e-mail. If this parameter is not set, it defaults to active.
This parameter stores auto reply text to be used by the user for the auto reply feature.
This parameter stores the auto reply expiration date in the following format:
MMDDYY:HH24:MI:SS:TZH:TZM
This parameter stores the e-mail addresses for the auto forward feature.
This parameter is associated with individual users and is present at the user level in Oracle Internet Directory, enabling OracleText configuration on a per user basis. This parameter is present at the domain level preferences for Users. The values set here are inherited by all new users in the domain during user creation time.
This parameter defines if the user is a regular user, a system administrator, or a domain administrator.
This parameter enables the user to have e-mail access outside the firewall.
Note: When a mail user is removed, any shared folders and public shared folders owned by that user are also deleted |
Perform the following steps to remove e-mail users:
Using the Thin Client, administrators can perform list management, such as create lists, modify list properties, delete lists, show lists, add and delete list members, show list members, and show all the lists a member is on.
To perform list management tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
Perform the following steps to create a list:
See Also:
"List Server Parameters" for parameter definitions |
Perform the following steps to edit list properties:
The following is a list of list server properties:
This parameter specifies the name of the distribution list.
This parameter specifies the person who owns or is responsible for the list.
This parameter specifies indicates the maximum size, in bytes, of a message delivered to a list. Any message larger than this size is rejected.
This parameter is a single line phrase describing the topic of discussions on this list.
This parameter is a multi-line text that is sent in a mail to users invited by a list owner to join their list.
This parameter is contains the list of users (mail IDs) who are the editors of the list.
This parameter is contains the list of users (mail IDs) who are the moderators of the list.
This parameter enables a list owner to support mail merge or scheduled mail delivery, this attribute contains the tag used for specifying mail merge and scheduler tags.
This parameter is set to true if the owner wants all subscription requests to be reconfirmed with the user.
This parameter specifies the type of the list. Possible values are:
This parameter denotes the type of subscription control on this list. Valid values are:
This parameter dines the level of control a list owner wants on who can post messages to their list. Valid values are open or subscriber.
Perform the following steps to delete a list:
Perform the following to steps to add or delete list members:
Perform the following steps to view all the lists belonging to a particular domain:
Perform the following steps to show list members:
Perform the following steps to show all the lists a user is on:
Using the Thin Client, administrators can perform alias management tasks, such as create, modify, and delete aliases.
To perform administration tasks for Oracle Email, administrators must navigate to the following URL:
http://<machine name>:<port>/um/traffic_cop
Perform the following steps to create a new alias.
Perform the following steps to edit alias properties:
Perform the following steps to delete aliases:
E-mail viruses typically have the form of an executable program as an e-mail attachment. The program gets executed on the client machine when the attachment is opened by an unsuspecting user, causing various forms of damage to the computer or the network. Oracle Email server contains a PL/SQL utility package MAIL_AV
that can scan and remove email viruses. To use this package, one simply writes a SQLPLUS script that uses this package or execute procedures in this package directly from SQLPLUS.
MAIL_AV
package allows users to identify virus messages using a variety of search criteria, such as subject, date, and size. Once messages with an attached virus are identified, the messages are moved to a designated folder away from their recipients. An administrator can manually examine the messages in the designated folder and remove them using any mail client. In cases where messages are wrongly identified as a virus, the MAIL_AV
package provides functions to restore the message back to the original recipient's folder.
Because MAIL_AV
has the ability to remove messages from regular users, it is considered a privileged package. Only sessions logged on as es_mail
database user can execute this package.
The following are summaries and usage examples for the procedures in the MAIL_AV
package:
The quarantine procedure has the following syntax:
PROCEDURE quarantine (p_endday IN DATE, p_dayrange IN NUMBER, p_attribute IN NUMBER, p_pattern IN VARCHAR2, p_folder IN VARCHAR2);
The quarantine procedure identifies virus messages using a given pattern and moves them to a designated folder. The caller of the procedure must have write authorization to the folder. Authentication is done by using MAIL_SESSION
package.
Parameters p_endday
and p_dayrange
can used to narrow down the virus search to within certain time frame. Parameter p_attribute
takes one of the following three values:
MAIL_AV.ATTR_SUBJECT MAIL_AV.ATTR_ATTACHMENT MAIL_AV.ATTR_SENDER
Parameter p_pattern
is the identifying string for the virus. Parameter p_folder
is the designated folder name to which virus-infected messages are moved.
The following example logs in as user SYSADMIN
, and scans the whole mail server for messages with an attachment name containing.exe
within the last seven days, and moves them to the /infected
folder.
declare sessionid number; begin mail_session.login('sysadmin', <password>, <ldaphost>, sessionid); mail_av.quarantine(sysdate, 7, mail_av.attr_attachment, '.exe', '/infected'); end; /
The Quarantine procedure can take on the following format enabling IMAP style search criteria:
PROCEDURE quarantine (p_criteria IN VARCHAR2, p_folder IN VARCHAR2);
This quarantine procedure form identifies virus messages using an IMAP style search criteria for enhanced searching. All IMAP search commands are supported. The advantage of using this procedure not only includes the expanded list of search item, but also the ability to combine search criteria using logical operations such as "and" or "or."
See Also:
Internet RFC 2060: Internet Message Access Protocol, version 4, rev 1, for more information on IMAP search commands |
Use the new form of quarantine procedure, the following script identifies and moves messages with subject "snow white" and from acme.com, that's also sent since Jan 2002:
declare sessionid number; begin mail_session.login('sysadmin', <password>, <ldaphost>, sessionid); mail_av.quarantine('SINCE 01-Jan-2002 SUBJECT "snow white" SENDER "aol.com"', '/infected'); end; /
There are two procedures to restore messages already quarantined back to their original folders:
PROCEDURE restore (p_messageid IN NUMBER); PROCEDURE restoreall;
The restore procedure takes a given message ID and restore it back to its original folder. If the message ID does not exist, the procedure does nothing. The restoreall
procedure restores all messages quarantined regardless which designated folders are used to store the messages. These procedures are useful when a message is wrongly identified as a virus message and must be restored back to its recipients.