Message Store Management

Skip to end of metadata
Go to start of metadata

Message Store Management

The message store is the component of the Messaging Server that contains the user mailboxes as well as the servers that provide IMAP, POP, and HTTP access to the mailboxes.

Note
Unless otherwise noted, the message store (specifically, the stored process) should be up and running while performing management and maintenance tasks described in Message Store Command-line Utilities.

The size of the message store increases as the number of users, mailboxes, and log files increase. You can control the size of the message store by specifying limits on the size of mailboxes, by specifying limits on the total number of messages allowed, and by setting aging policies for messages in the store.

Depending on the number of users your server supports, the message store might require one physical disk or multiple physical disks. There are two ways to integrate this additional disk space into your system. The easiest way is to add additional message store partitions (see Managing Message Store Partitions and Adding Storage) Likewise, if you are supporting multiple hosted domains, you might want to dedicate a server instance to a single, large domain. With this configuration, you can designate a store administrator for a particular domain. You can also expand the message store by adding more partitions.

Topics:

Message Store Pages by Topic

Page: Message Store Administration
Page: Message Store Administration in Unified Configuration
Page: Message Store Architecture and Concepts
Page: Message Store Architecture and Concepts in Unified Configuration
Page: Message Store Backup and Restore
Page: Message Store Command-line Utilities
Page: Message Store Message Expiration
Page: Message Store Message Types Overview
Page: Message Store Quota (Overview)
Page: Message Store Quota (Overview) in Unified Configuration
Page: Message Store Shared Folders Overview
Page: Migrating Mailboxes to a New System
Page: Monitoring the Message Store
Page: Quotas & Automatic Mail Deletion
Page: Troubleshooting the Message Store
Page: Upgrading the Message Store

All Message Store Pages

Overview and Concepts
Page: Message Store Administration
Page: Message Store Administration in Unified Configuration
Page: Message Store Architecture and Concepts
Page: Message Store Architecture and Concepts in Unified Configuration
Page: Message Store Automatic Recovery on Startup
Page: Message Store Command-line Utilities
Page: Message Store Directory Layout
Page: Message Store Load Throttling
Page: Message Store Logging
Page: Message Store Maintenance Queue
Page: Message Store Message Types Overview
Page: Message Store Shared Folders Overview
Page: Message Store Valid UIDs and Folder Names
Page: Upgrading the Message Store
Message Store Tasks and Examples
Page: Backing Up and Restoring the Message Store
Page: Best Practices for Messaging Server and ZFS
Page: Configuring Message Expiration
Page: Configuring POP, IMAP, and HTTP Services
Page: Managing Mailboxes
Page: Managing Message Store Partitions and Adding Storage
Page: Managing Message Store Quotas
Page: Managing Message Store Quotas in Unified Configuration
Page: Managing Message Types in the Message Store
Page: Managing Message Types in the Message Store in Unified Configuration
Page: Managing Shared Folders
Page: Managing Shared Folders in Unified Configuration
Page: Migrating Mailboxes to a New System
Page: Monitoring Disk Space
Page: Monitoring the Message Store
Page: Monitoring User Access to the Message Store
Page: moveuser
Page: Protecting Mailboxes from Deletion or Renaming
Page: Reducing Message Store Size Due to Duplicate Storage
Page: Specifying Administrator Access to the Message Store
Page: Troubleshooting the Message Store
Labels:
messagestore messagestore Delete
messagingserver messagingserver Delete
administering administering Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.