By default, mailboxes are created in the primary partition. If the partition gets full, additional messages cannot be stored. There are several ways to address the problem:
Reduce the size of user mailboxes
If you are using volume management software, add additional disks
Create additional partitions (To Add a Partition) and move mailboxes to the new partitions
If possible, we recommend adding additional disk space to a system using volume management software since this procedure is the most transparent for the user. However, you may also move mailboxes to a different partition.
Make sure user is disconnected from their mailbox during the migration process. This can be done by informing the user to log off and stay off during mailbox move, or, by setting the mailAllowedServiceAccess attribute so that POP, IMAP and HTTP services are disallowed after they are logged off. (See mailAllowedServiceAccess in Sun Java System Communications Services 6 2005Q4 Schema Reference.
Setting mailAllowedServiceAccess to disallow POP, IMAP, HTTP access does not disconnect any open connections to the mailbox. You must make sure that all connections are closed prior to the moving mailboxes.
Move the user mailbox with the following command:
mboxutil -r user/<userid>/INBOX user/<userid>/INBOX <partition_name>
Example:
mboxutil -r user/ofanning/INBOX user/ofanning/INBOX secondary
Set the mailMessageStore attribute in the moved user’s LDAP entry to the name of the new partition.
Example: mailMessageStore: secondary
Inform the user that message store connection is now allowed. If applicable, change the mailAllowedServiceAccess attribute to allow POP, IMAP and HTTP services.