Previous Contents Index Next |
iPlanet Messaging Server 5.2 Reference Manual |
Chapter 1 Messaging Server Command-line Utilities
iPlanet Messaging Server provides a set of command-line utilities in addition to its graphical user interface. This chapter describes utilities for messaging server starting, stopping, administration, message access, and message store.
For descriptions of the command-line utilities for the MTA, see Chapter 2 "Message Transfer Agent Command-line Utilities." For descriptions of the iPlanet Delegated Administrator for Messaging command-line utilities, see Chapter 3 "Delegated Administrator Command-line Utilities."
The commands described in this chapter are listed in Table 1-1.
Command Descriptions
This section describes what the main iPlanet Messaging Server command-line utilities do, defines their syntax, and provides examples of how they are used. The utilities are listed in alphabetical order.
configutil
The configutil utility enables you to list and change iPlanet Messaging Server configuration parameters.
For a list of all configuration parameters, see Chapter 4 "Messaging Server Configuration."
Most iPlanet Messaging Server configuration parameters and values are stored in the LDAP database on Directory Server with the remaining parameters and values stored locally in the msg.conf and local.conf files. The startup parameters are stored in the msg.conf file and are set during installation. The local.conf files should not be edited manually. Use configutil to edit the parameters stored in those files.
Requirements: Must be run locally on the Messaging server.
Location: server-root/bin/msg-instance/configutil
You can use configutil to perform four tasks:
Display particular configuration parameters using -o option.
Add ;lang-xx after the option to list parameters with a specified language parameter. For example, ;lang-jp to list options specified for the Japanese language.
List configuration parameter values using the -l or -p prefix options.
Use -l to just list local configuration parameters from the server's local configuration file.
Use -p prefix to just list those configuration parameters whose names begin with the letters specified in prefix.
Set configuration parameters using the -o option and -v value options.
Include the -l option with -o option and -v value to store the new value in the server's local configuration file.
To read the actual value from stdin, specify a dash (-) as the value on the command line.
Add ;lang-xx after the option to set options for a specified language parameter. For example, ;lang-jp to set options specified for the Japanese language.
Import configuration parameter values from stdin using the -i option.
Include the -l option with the -i option to import all configuration parameters to the server's local configuration file.
Options
The options for this command are:
If you specify no command-line options, all configuration parameters are listed.
Examples
To list all configuration parameter and their values in the both the Directory Server LDAP database and local server configuration file:
configutil
To import configurations from an input file named config.cfg:
configutil -i < config.cfg
To list all configuration parameters with the prefix service.imap:
configutil -p service.imap
To display the value of the service.smtp.port configuration parameter:
configutil -o service.smtp.port
To set the value of the service.smtp.port configuration parameter to 25:
configutil -o service.smtp.port -v 25
To clear the value for the service.imap.banner configuration parameter:
configutil -o service.imap.banner -v ""
Language Specific Options
To list or set options for a specific language, append ;lang-xx immediately after the option with no spaces, where xx is the two-letter language identifier. For example, to view the text of the Japanese version of the store.quotaexceededmsg message:
configutil -o "store.quotaexceededmsg;lang-jp"
counterutil
The counterutil utility displays and changes counters in a counter object. It can also be used to monitor a counter object every 5 seconds.
Requirements: Must be run locally on the Messaging server.
Location: server-root/bin/msg/admin/bin
counterutil -o counterobject [-i interval] [-l] [-n numiterations]
[-r registryname]
Options
The options for this command are:
Examples
To list all counter objects in a given server's counter registry:
counter
To display the content of a counter object imapstat every 5 seconds:
counterutil -o imapstat -r \
server-root/msg-instance/counter/counter
deliver
The deliver utility delivers mail directly to the message store accessible by IMAP or POP mail clients.
If you are administering an integrated messaging environment, you can use this utility to deliver mail from another MTA, a sendmail MTA for example, to the Messaging Server message store.
Requirements: Must be run locally on the Messaging Server; the stored utility must also be running. Make sure that the environment variable CONFIGROOT is set to server-root/msg-instance/config.
Location on UNIX: server-root/bin/msg/store/bin
deliver [-l] [-c] [-d] [-r address] [-f address] [-m mailbox] [-a authid]
[-q] [-g flag] [userid]
Options
The options for this command are:
If you specify no options, mail is delivered to the inbox.
Examples
To deliver the contents of a file named message.list to Fred's tasks mailbox:
deliver -m tasks fred < message.list
In the above example, if the tasks mailbox does not grant "p" rights to the sender, the contents of message.list are delivered to the inbox of the user fred.
hashdir
The hashdir command identifies the directory that contains the message store for a particular account. This utility reports the relative path to the message store. The path is relative to the directory level just before the one based on the user ID. hashdir sends the path information to standard output.
Requirements: Must be run locally on the messaging server. Make sure that the environment variable CONFIGROOT is set to server-root/msg-instance/config.
hashdir [-a] [-i] account_name
Options
The options for this command are:
Option
Description
iminitquota
The iminitquota utility reinitializes the quota limit from the LDAP directory and recalculates the total amount of disk space that is being used by the users. It updates the message store quota.db database under the mboxlist directory in the message store. The iminitquota utility should be run after the reconstruct -q utility is run.
Options
The options for this command are:
You must specify either the -a or -u option with the iminitquota command.
imsasm
The imsasm utility is an external ASM (Application Specific Module) that handles the saving and recovering of user mailboxes. imsasm invokes the imsbackup and imsrestore utilities to create and interpret a data stream.
During a save operation imsasm creates a save record for each mailbox or folder in its argument list. The data associated with each file or directory is generated by running the imsbackup or imsrestore command on the user's mailbox.
imsasm [standard_asm_arguments]
Options
The options used in the imsasm utility are also known as standard-asm-arguments, which are Legato NetWorker® backup standards.
Either -s (saving), -r (recovering), or -c (comparing) must be specified and must precede any other options. When saving, at least one path argument must be specified. path may be either a directory or filename.
The following options are valid for all modes:
When saving (-s), the following options may also be used:
When recovering (-r), the following options may also be used:
Examples
To use imsasm to save the mailbox INBOX for user joe, the system administrator creates a directory file backup_root/backup/DEFAULT/joe/.nsr with the following contents:
imsasm: INBOX
This causes the mailbox to be saved using imsasm. Executing the mkbackupdir utility will automatically create the .nsr file. See mkbackupdir.
imsbackup
The imsbackup utility is used to write selected contents of the message store to any serial device, including magnetic tape, a UNIX pipe, or a plain file. The backup or selected parts of the backup may later be recovered via the imsrestore utility. The imsbackup utility provides a basic backup facility similar to the UNIX tar command.
Location: server-root/bin/msg/store/bin
For more information about imsbackup and backing up the message store, see the section "Backing Up and Restoring the Message Store" in the iPlanet Messaging Server Administrator's Guide.
imsbackup -f device|- [-a userid] [-b blocking_factor] [-d datetime] [-i]
[-l] [-m link_count] [-u file] [-v] [path]
Options
The options for this command are:
Examples
The following example backs up joe to /dev/rmt/0:
imsbackup -f /dev/rmt/0 /mystore/ALL/joe
mystore maps to the default partition.
The following example backs up all users under groupA to backupfile:
imsbackup -f- /mystore/groupA > backupfile
The following example performs a full backup of the message store instance mystore:
imsbackup -f /dev/rmt/0 /mystore
imsexport
The imsexport utility exports iPlanet Messaging Server mailboxes into UNIX /var/mail format folders.
The imsexport utility extracts the messages in a message store folder and writes the messages to a UNIX file under the directory specified by the administrator. The file name is the same name as the IMAP folder name. For message store folders that contain both messages and sub-folders, imsexport creates a directory with the folder name and a file with the folder name plus a .msg extension. The folder.msg file contains the messages in the folder. The folder directory contains the sub-folders.
imsexport -d dir -u user [-a user] [-c y|n] [-g] [-s mailbox] [-v mode]
Options
The options for this command are:
Example
In the following example, imsexport extracts all email for user smith1. smith1 is a valid user account in the iPlanet Messaging Server message store. User smith1 has three folders on the store: INBOX (the normal default user folder), private, and private/mom. The destination directory will be /tmp/joes_mail.
% imsexport -u smith1 -d /tmp/joes_mail/
imexport then transfers each message store folder into a /var/mail conforming file. Thus you will get the following files:
imsimport
The imsimport utility migrates UNIX /var/mail format folders into an iPlanet Messaging Server message store.
The imsimport utility extracts the messages stored in /var/mail mailboxes and appends them to the corresponding users' folder in the iPlanet Messaging Server message store. Files in the directory that are not in the standard UNIX mailbox format are skipped. If the corresponding users do not exist in the message store, imsimport creates them. When the user quota is exceeded, imsimport bypasses the message store quota enforcement, so the user does not receive an "over quota" message.
imsimport -u user -s file [-a user] [-c y|n] [-d mailbox] [-g] [-n]
[-v mode]
Options
The options for this command are:
Examples
imsimport migrates the specified /var/mail/folder for the specified user to the iPlanet Messaging Server message store. If the destination folder is not specified, imsimport calls the destination folder by the same name as the source folder. In the following example, the command migrates the default /var/mail INBOX for the user smith, to the INBOX.
imsimport -u smith -s /var/mail/smith -d INBOX
Similarly, if you are trying to move a folder called test from /home/smith/folders/ to the iPlanet Messaging Server message store, use the following command:
imsimport -u smith -s /home/smith/folders/test -d test
If a destination folder called test already exists in the iPlanet Messaging Server message store, imsimport appends the messages to the existing folder in the mailbox.
imsrestore
The imsrestore utility restores messages from the backup device into the message store.
Location: server-root/bin/msg/store/bin
imsrestore -f device|- [-a userid] [-b blocking_factor] [-c y | n]
[-h] [-i] [-m file] [-n] [-t] [-u file]
[-v 0|1|2] [path]
Options
The options for this command are:
Examples
The following example restores the messages from the file backupfile:
imsrestore -f backupfile
The following example restores the messages for user1 from the file backupfile:
imsrestore -f backupfile /mystore/ALL/user1
The following example lists the content of the file backupfile:
imsrestore -f backupfile -t
The following example renames users in the file mapfile:
imsrestore -m mapfile -f backupfile
where the mapfile format is oldname=newname:
userA=user1
userB=user2
userC=user3
imscripter
The imscripter utility connects to an IMAP server and executes a command or a sequence of commands.
Requirements: May be run remotely.
Location: server-root/bin/msg/admin/bin
imscripter [-h] [-f script | [-c command] -f datafile]] [-c command]
[-s serverid | -p port | -u userid | -x passwd | -v verbosity]
Options
The options for this utility are:
mboxutil
The mboxutil command lists, creates, deletes, renames, or moves mailboxes (folders). mboxutil can also be used to report quota information.
You must specify mailbox names in the following format:
userid is the user that owns the mailbox and mailbox is the name of the mailbox.
Requirements: Must be run locally on the messaging server; the stored utility must also be running.
Location: server_root/bin/msg/admin/bin
mboxutil [-a] [-c mailbox] [-d mailbox] [-f file] [-g group]
[-r oldname newname [partition]] [-l] [-p pattern] [-q domain] [-x]
[-k cmd mailbox] [-u [userid]]
Options
The options for this command are:
Examples
To list all mailboxes for all users:
mboxutil -l
To list all mailboxes and also include path and acl information:
mboxutil -l -x
To create the default mailbox named INBOX for the user daphne:
mboxutil -c user/daphne/INBOX
To delete a mail folder named projx for the user delilah:
mboxutil -d user/delilah/projx
To delete the default mailbox named INBOX and all mail folders for the user druscilla:
mboxutil -d user/druscilla/INBOX
To rename Desdemona's mail folder from memos to memos-april:
mboxutil -r user/desdemona/memos user/desdemona/memos-april
To lock a mail folder named legal for the user dulcinea:
mboxutil -k user/dulcinea/legal cmd
where cmd is the command you wish to run on the locked mail folder.
To move the mail account for the user dimitria to a new partition:
mboxutil -r user/dimitria/INBOX user/dimitria/INBOX partition
where partition specifies the name of the new partition.
To move the mail folder named personal for the user dimitria to a new partition:
mboxutil -r user/dimitria/personal user/dimitria/personal \
partition
To list usage statistics:
mboxutil -u daphne
diskquota size(K) %use msgquota msgs %use user
10240 297 no quota 953 29% daphne
mkbackupdir
The mkbackupdir utility creates and synchronizes the backup directory with the information in the message store. It is used in conjunction with Solstice Backup (Legato Networker). The backup directory is an image of the message store. It does not contain the actual data. mkbackupdir scans the message store's user directory, compares it with the backup directory, and updates the backup directory with the new user names and mailbox names under the message store's user directory.
The backup directory is created to contain the information necessary for Networker to backup the message store at different levels (server, group, user, and mailbox). Figure 1-1 displays the structure.
Figure 1-1    Backup directory hierarchy
Location: server_root/bin/msg/store/bin
The variables in the backup directory contents are:
The mkbackupdir utility creates:
A default group directory (ALL) or the group directories defined in the backup-groups.conf configuration file. The following is a sample backup-groups.conf file:
groupA=a*
groupB=b*
groupC=c*
.
.
.
A user directory under the backup directory for each new user in the message store.
A 0 length mailbox file for each mailbox.
A .nsr file for each subdirectory that contains user mailboxes. The .nsr file is the NSR configuration file that informs the Networker to invoke imsasm. imsasm then creates and interprets the data stream.
Each user mailbox contains files of zero length. This includes the INBOX, which is located under the user directory.
Note Make sure the backup directory is writable by the message store owner (mailsrv).
mkbackupdir [-a userid] [-i | -f] [-g] [-v] -p directory
Options
The options for this command are:
Examples
To create the mybackupdir directory, enter the following:
mkbackupdir -p /mybackupdir
MoveUser
The MoveUser utility moves a user's account from one messaging server to another. When user accounts are moved from one messaging server to another, it is also necessary to move the user's mailboxes and the messages they contain from one server to the other. In addition to moving mailboxes from one server to another, MoveUser updates entries in the directory server to reflect the user's new mailhost name and message store path.
Requirements: May be run remotely.
Location: server-root/bin/msg/admin/bin
MoveUser -s srcmailhost[:port] -x proxyuser -p password -d destmailhost[:port]
[-u uid | -u uid -U newuid| -l ldapURL -D binDN -w password
[-r DCroot -t defaultDomain]]
Options
The options for this command are:
Examples
To move all users from host1 to host2, based on account information in the Directory Server siroe.com:
MoveUser -l \
"ldap://siroe.com:389/o=siroe.com???(mailhost=host1.domain.com)" \
-D "cn=Directory Manager" -w password -s host1 -x admin \
-p password -d host2 -a admin -v password
To move one user from host1 which uses port 150 to host2, based on account information in the Directory Server siroe.com:
MoveUser -l \
"ldap://siroe.com:389/o=siroe.com???(uid=userid)" \
-D "cn=Directory Manager" -w password -s host1:150 -x admin \
-p password -d host2 -a admin -v password
To move a group of users whose uid starts with letter `s' from host1 to host2, based on account information in the Directory Server server1.siroe.com:
MoveUser -l \
"ldap://server1.siroe.com:389/o=siroe.com???(uid=s*)" \
-D "cn=Directory Manager" -w password -s host1 -x admin \
-p password -d host2 -a admin -v password
To move a user's mailboxes from host1 to host2 when the user ID of admin is specified in the command line:
MoveUser -u uid -s host1 -x admin -p password -d host2 -a admin \
-v password
To move a user named aldonza from host1 to a new user ID named dulcinea on host2:
MoveUser -u aldonza -U dulcinea -s host1 -x admin -p password \
-d host2 -a admin -v password
quotacheck
The quotacheck utility calculates the total mailbox size for each user in the message store. This utility can also compare mailbox size with a user's assigned quota. As an option, you can email a notification to users who have exceeded a set percentage of their assigned quota.
Requirements: Must be run as the message store owner. This utility depends on the iPlanet Messaging Server shared libraries. Set the LD_LIBRARY_PATH or SHLIB_PATH appropriately. These libraries are located in: server-root/bin/msg/lib.
Dependencies: The delivery agent's quota warning mechanism needs to be turned off in order for quotacheck to work, because the quotacheck and the delivery agent use the same element in the quota database to record last-warn time. To turn off the delivery agent's quota warning, remove the attribute value for nsmsgquotaexceededmsg;lang-en in the directory.
Location: server-root/bin/msg/admin/bin
Syntax
The following form of quotacheck should be used when you want to notify users if they have exceeded a set percentage of their assigned quota.
quotacheck [-e] [-d domain] [-r rulefile] [-t message template] [-D] -n
This following of quotacheck should be used when you want to report the usage to stdout.
quotacheck [-e] [-d domain][-r rulefile] [-t message template] [-i] [-v]
[-h] [-u user] [-D]
Options
The options for this command are:
Option
Description
Allows extended reporting. Per folder usage is included in the report.
Specifies the set of rules to be used when you want to calculate quota usage. If -r is not specified, a default rulefile can be used. To setup a default rulefile, copy the "Sample Rulefile" to server-root/msg-instance/config. See "Rulefile Format".
Notifies users when their mailbox quota is exceeded. The message template format is the following:
%U% - user's mailbox id
%Q% - percentage of the used mailbox quota
%R% - quota usage details: assigned quota, total mailbox size, and percentage used. If the -e is specified, mailbox usage of the individual folders are also reported.
If -t is not specified, a default message file will be mailed. To setup a default message file, copy the "Notification File" to server-root/msg-instance/config.
Sends notification messages based on the rules defined in the rulefile. If you do not define any rules when you use this option, you will receive an error.
Ignores the rulefile and any active rule defined in it. The quota status of all the users in the message store will be printed to stdout. This option can only be used when you want to report usage. If -i is not specified, the active rule with the least threshold is used to print a list of all of the users and their quota status to stdout.
Prints the username, quota, total mailbox size and percentage of mailbox used by all of the users. When you are using quotacheck to report usage, it will default to this option if no other options are specified.
Obtains the quota status of the specified user id. Can be used with -e for extended reporting on the user. Can be used multiple times to specify multiple users. For example: quotacheck -u user1 -u user2 -u user3
Examples
To send a notification to all users in accordance to the default rulefile:
quotacheck -n
To send a notification to all users in accordance to a specified rulefile, myrulefile, and to a specified mail template file, mytemplate.file:
quotacheck -n -r myrulefile -t mytemplate.file
To list the usage of all users whose quota exceeds the least threshold in the rulefile:
quotacheck
To list the usage of all users and (will ignore the rulefile):
quotacheck -i
To list per folder usages for users user1 and user2 (will ignore the rulefile):
quotacheck -u user1 -u user2 -e
To only list the users in domain siroe.com:
quotacheck -d siroe.com -i
Rulefile Format
The rulefile format is organized into two sections: a general section and a rule name section. The general section contains attributes that are common across all rules. Attributes that are typically specified in the general section are the mailQuotaAttribute and the reportMethod. In the rule name section, you can write specific quota rules for notification intervals, trigger percentages, and so on. Attributes that are typically specified in the rule name section are notificationTriggerPercentage, enabled, notificationInterval, and messageFile. Note that the attributes and corresponding values are not case-sensitive. The following rulefile format is used:
[General]
mailQuotaAttribute = [value]
reportMethod = [value]
[rulename1]
attrname=[value]
attrname=[value]
[rulename2]
attrname=[value]
attrname=[value]
[rulename3]
attrname=[value]
attrname=[value
General Attribute
Required Attribute?
Default Value
Description
Specifies the name of the custom mailquota attribute. If not specified, the value in quotadb is used.
Can customize the output of the quota report. The value of this attribute is specified as library-path:function, where library-path is the path of the shared library and function is the name of the report function. See "reportMethod Signature" to see the structure of the attribute.
Rule Attribute
Required Attribute?
Default Value
Description
Specifies the consumed quota percentage that will trigger notification. Value should be unique and an integer.
Indicates the number of hours before a new notification is generated.
Indicates if the particular rule is active. Applicable values are 0 for FALSE and 1 for TRUE.
Can customize the overquota notification method to send to the user. The value of this attribute is specified as library-path:function, where library-path is the path of the shared library and function is the name of the report function.
See "notificationMethod Signature" to see the structure of the attribute.
reportMethod Signature
The following signature can be used for the reportMethod():
The address, message, points to the output message. The report function is expected to fill the value of *message and allocate memory for message when necessary. The freeflag variable indicates if the caller is responsible for freeing allocated memory for *message.
The return values are 0 for success and 1 for failure.
The quotacheck function will invoke the reportMethod to generate the report output. If the reportMethod returns 0 and *message is pointing to a valid memory address, message will be printed.
If the *freeflag is set to 1, the caller will free the memory address pointed to by message. If the -e option is specified, the quota usage for every folder will be stored in the folderlist, an array in FolderUsage; the num_folder variable is set to the number of folders in the folderlist.
notificationMethod Signature
The following signature can be used for the notificationMethod():
The address, message, points to the notification message. The notification function is expected to fill in the value of this variable and allocate the memory for the message when necessary. The freeflag variable indicates if the caller is responsible for freeing the memory allocated for message.
The return values are 0 for success and 1 for failure.
If the notification function returns a 0, and *message is pointing to a valid address, the quotacheck utility will deliver the message to the user. If the *freeflag is set to 1, the caller will free the memory address pointed to by message after the message is sent.
If the -e option is specified, the quota usage for every folder will be stored in the folderlist variable, an array of FolderUsage structure; the num_folder variable is set to the number of folders in the folderlist.
Note If the messageFile attribute is also specified, the attributed messageFile will be ignored.
Sample Rulefile
#
# Sample rulefile
#
[General]
mailQuotaAttribute=mailquota
reportMethod=/xx/yy/libzz.so:myReportMethod [for Solaris only ]
/xx/yy/libzz.sl:myReportMethod [for HP-UX only]
\xx\yyi ibzz.dll:myReportMethod [for Windows NT only]
[rule1]
notificationTriggerPercentage=60
enabled=1
notificationInterval=3
notificationMethod=/xx/yy/libzz.so:myNotifyMethod_60
[rule2]
notificationTriggerPercentage=80
enabled=1
notificationInterval=2
messageFile=/xx/yy/message.txt
[rule3]
notificationTriggerPercentage=90
enabled=1
notificationInterval=1
notificationMethod=/xx/yy/libzz.so:myNotifyMethod_90
Threshold Notification Algorithm
Rule precedence is determined by increasing trigger percentages.
The highest applicable threshold is used to generate a notification. The time and the rule's threshold are recorded.
If users move into a higher threshold since their last quota notification, a new notification will be delivered based on the current set of applicable rules. This notice can be immediately delivered to any user whose space usage is steadily increasing.
If usage drops, the notification interval of the current rule (lower threshold) will be used to check the time elapsed since the last notice.
The stored time and threshold for the user will be reset to zero if the user's mailbox size falls below all of the defined thresholds.
Notification File
The utility depends on the message file to have at minimum a Subject Header. There should be at least one blank line separating the Subject from the body. The other requires headers are generated by the utility/ The notification file format is the following:
Subject: [Warning] quota reached for %U%
Hello %U%,
Your quota: %C%
Your current mailbox usage: %M%
Your mailbox is now %Q% full. The folders consuming the most space are: %R%.
Please clean up unwanted diskspace.
Thanks,
-Administrator
readership
The readership utility reports on how many users other than the mailbox owner have read messages in a shared IMAP folder.
An owner of an IMAP folder may grant permission for others to read mail in the folder. A folder that others are allowed to access is called a shared folder. Administrators can use the readership utility to see how many users other than the owner are accessing a shared folder.
The utility scans all mailboxes.
This utility produces one line of output per shared folder, reporting the number of readers followed by a space and the name of the mailbox.
Each reader is a distinct authentication identity that has selected the shared folder within the past specified number of days. Users are not counted as reading their own personal mailboxes. Personal mailboxes are not reported unless there is at least one reader other than the folder's owner.
Requirements: Must be run locally on the messaging server; the stored utility must also be running.
Location: server-root/bin/msg/admin/bin
readership [-d days] [-p months]
Options
The options for this command are:
reconstruct
The reconstruct utility rebuilds one or more mailboxes, or the master mailbox file (the mailboxes database), and repairs any inconsistencies. You can use this utility to recover from almost any form of data corruption in the message store.
A mailbox consists of files under the user partition directory. The mailboxes database is the mboxlist database.
Requirements: Must be run locally on the messaging server; the stored utility must also be running.
Location: server-root/bin/msg/admin/bin
Note Low-level database repair, such as completing transactions and rolling back incomplete transactions is performed with stored -d.
reconstruct [-n | -f] [-p partition] -r [mailbox [mailbox...]] reconstruct [-n | -f] [-p partition] mailbox [mailbox...] reconstruct [-p partition] -m reconstruct -q reconstruct -o [-d filename]
Options
The options for this command are:
The mailbox argument indicates the mailbox to be repaired. You can specify one or more mailboxes. Mailboxes are specified with names in the format user/userid/sub-mailbox, where userid is the user that owns the mailbox. For example, the inbox of the user dulcinea is entered as: user/dulcinea/INBOX.
Examples
The following command performs a reconstruct on a specific mailbox:
reconstruct user/dulcinea/INBOX
The following checks the specified mailbox, without performing a reconstruct:
reconstruct -n user/dulcinea/INBOX
The following command checks all mailboxes in the message store:
reconstruct -n -r
start-msg
The start-msg utility starts all of the messaging server processes (smtp, imap, pop, store, http, ens), or optionally, one specified service.
start-msg [smtp | imap | pop | store | http | ens]
Examples
The following command starts all the messaging server processes:
start-msg
The following command starts the imap process:
start-msg imap
stop-msg
The stop-msg utility stops all messaging server processes (smtp, imap, pop, store, http, ens), or optionally, one specified service.
stop-msg [smtp | imap | pop | store | http | ens]
Examples
The following command stops all messaging server processes:
stop-msg
The following command stops the http service:
stop-msg http
stored
The stored utility performs the following functions:
Background and daily messaging tasks
Deadlock detection and rollback of deadlocked database transactions
Cleanup of temporary files on startup
Implementation of aging policies
Periodic monitoring of server state, disk space, service response times, and so on The stored utility automatically performs cleanup and expiration operations once a day at midnight. You can choose to run additional cleanup and expiration operations.
Requirements: Must be run locally on the Messaging Server.
Location: server-root/bin/msg/admin/bin
Syntax
To run stored from the command line to perform a specific operation:
stored [-1] [-c] [-n] [-v [-v]]
To run stored as a daemon process:
stored [-d] [-v [-v]]
Options
The options for this command are:
Examples
To test expiration policies:
stored -n
To perform a single aging and cleanup pass:
stored -l -v
Previous Contents Index Next
Copyright © 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated August 15, 2002