Represents messaging servers (such as NetWare MHS servers).
|
Class Flags |
Setting |
|---|---|
|
Container |
Off |
|
Effective |
On |
|
Nonremovable |
On |
|
Ambiguous Naming |
Off |
|
Ambiguous Container |
Off |
|
Auxiliary Class |
Off |
|
Rule |
Class/Attribute |
Defined For |
|---|---|---|
|
Super Classes |
Messaging Server |
|
|
Containment |
||
|
Named By |
|
Messaging Server |
Inherited from Top |
Inherited from Server |
|---|---|---|
|
(None) |
|
Messaging Server |
|
|---|---|
|
Inherited from Top |
|
|---|---|
|
Inherited from Server |
|
|---|---|
|
Object Name |
Default Rights |
Affected Attributes |
Class Defined For |
|---|---|---|---|
|
[Creator] |
Supervisor |
[Entry Rights] |
|
|
[Public] |
Read |
Network Address |
|
|
[Self] |
Supervisor |
[Entry Rights] |
|
|
[Self] |
Read/Write |
Status |
Messaging Server |
|
[Self] |
Browse |
[Entry Rights] |
Messaging Server |
|
[Self] |
Read |
[All Attributes] |
Messaging Server |
|
[Public] |
Read |
Messaging Server Type |
Messaging Server |
|
[Public] |
Read |
Messaging Database Location |
Messaging Server |
For help in understanding the class definition template, see Reading Class Definitions.
A MHS messaging server picks up messages, which are either submitted by messaging applications (for example, E-mail) or transferred from another messaging server, and delivers them to the recipients. For recipients whose mailboxes are local on the messaging server, the messages are delivered to their mailboxes. Otherwise, the messaging server transfers the messages to another messaging server for eventual delivery to the recipient’s mailbox.
A MHS messaging server runs as mhs nlm on a NetWare server. There is no limit to the number of mailboxes it serves, except that mailboxes take up disk space.
A MHS messaging server is represented by a eDirectory leaf object whose object class is Messaging Server.
The Host Device attribute (inherited from Server) identifies the NCP Server on which the messaging server’s software runs.
The Message Routing Group attribute names the message routing groups to which the messaging server belongs.
The Messaging Database Location attribute names the volume and path (such as sys:mhs) on which the message directory resides. MHS messaging servers use a file system subtree to (1) receive messages from applications, other messaging servers and gateways, (2) store messages while they are being routed, (3) store internal control files, and (4) to extract files.
The Messaging Server Type attribute identifies the type of the Messaging Server object (for example, MHS, GMHS, X400).
The Postmaster attribute specifies one or more users who have the privileges to manage the messaging server, such as privileges to remove a mailbox. Postmasters also receive messages about special events in the messaging server, such as messages not being processed.
The Supported Gateway attribute specifies the messaging gateways that are connected through the messaging server. It provides messaging connectivity between the MHS messaging system and foreign messaging systems.
The Supported Services attribute indicates the messaging capabilities of the server.
The User attribute (inherited from Server) contains a list users whose mailboxes are serviced by the messaging server. Any effective object that has the Mailbox ID and Mailbox Location attributes is a valid value for this list.
Adding an object to the User list has the same effect as assigning values to the object’s Mailbox Location and Mailbox ID attributes. An administrator can give an object a mailbox by either means.
For LDAP clients to access this class, the LDAP server must map this class to a name that contains no spaces or colons.