M

(n.) The programs that help users send and receive
email. The mail client is the part of the various networks and mail
programs with which users have the most contact. Mail clients create
and submit messages for delivery, check for new incoming mail, and
accept and organize incoming mail.

(n.) An SNMP data
element that forms part of an MIB.
In Directory Server, the managed objects are held in cn=monitor,
and the SNMP agent provides the objects to the network management
station. As with LDAP attributes, each managed object has a name and
object identifier expressed in dot notation.

(message-driven bean) (n.) An enterprise bean that
is an asynchronous message consumer. A message-driven bean has no
state for a specific client, but its instance variables might contain
state across the handling of client messages, including an open database
connection and an object reference to an object based on the EJBTM architecture. A client accesses a message-driven bean
by sending messages to the destination for which the message-driven
bean is a message listener.

(1) (n.) The fundamental unit of email that consists of a header and a body and is often contained in an envelope while it is in transit from the sender to the recipient.

(2) (n.) In the Java Message Service, an asynchronous
request, report, or event consumed by a JMS client.
A message has a header (to which additional fields can be added) and
a body. The message header specifies standard fields and optional
properties. The message body contains the data that is being transmitted. A message contains vital
information needed to coordinate enterprise applications, in the form
of precisely formatted data that describes specific business actions.

message access services

(n.) The protocol servers, software drivers, and libraries
that support client access to the Messaging Server message store.

(n.) The act that occurs when an MTA sends a message delivered to a particular
account to one or more new destinations as specified by the account’s
attributes. Forwarding might be configurable by the user. See also message delivery, message routing.

(n.) The messaging system that implements the JavaTM Message Service (JMS) open standard. Sun Java System Message
Queue is a JMS provider.

message queue

(n.) The directory where messages accepted from clients
and other mail servers are queued for immediate or deferred delivery.

Message Queue client runtime

(n.) Software that provides JMS clients with an interface
to the Java Enterprise System message server. The client runtime supports all
operations needed for clients to send messages to destinations and
to receive messages from such destinations.

Message Queue message server

(n.) Software that provides delivery services for
a Message Queue messaging system, including connections to JMS clients,
message routing and delivery, persistence, security, and logging.
The message server maintains physical destinations to which JMS clients
send messages, and from which the messages are delivered to consuming
clients.

message quota

(n.) A limit defining how much disk space a particular
folder can consume.

message routing

(n.) The act of transferring a message from one MTA to another when the first MTA determines
that the recipient is not a local account, but might exist elsewhere.
Routing is normally configurable only by a network administrator.
See also message forwarding.

message selector

(n.) A way for a consumer to select messages based
on property values (selectors) in JMS message headers. A message service
performs message filtering and routing based on criteria placed in
message selectors.

(n.) The database of all locally delivered messages
for a Messaging Server instance. Messages can be stored on a single
physical disk or stored across multiple physical disks.

message store administrator

(n.) A user who has administrative privileges to manage
the message store for a Messaging Server installation. This user can
view and monitor mailboxes and specify access control to the store.
Using proxy authorization rights, this user can run certain utilities
for managing the store.

message store partition

(n.) A message store or subset of a message store
residing on a single physical file system partition.

message submission

(n.) The client userAgent transfers
a message to the mail server and requests delivery.

(n.) The administrator whose privileges include installation
and administration of a Messaging Server instance.

messaging server base directory

(n.) The directory into which all servers associated
with a given Administration Server on a given host are installed.
Typically designated msg_svr_base. See
also installation directory.

Messenger Express

(n.) A mail client that enables users to access their
mailboxes through a browser-based (HTTP) interface. Messages, folders,
and other mailbox information are displayed in HTML in a browser window.
See also webmail.

Messenger Express Multiplexor

(n.) A proxy messaging server that acts as a Multiplexor.
The server allows you to connect to the HTTP service of Messaging
Server (Messenger Express). The Messenger Express Multiplexor facilitates
distributing mail users across multiple server machines.

metadata

(n.) Information about a component, such as the component’s
name and specifications for component behavior. See also deployment descriptor.

metadevice state database replica

(n.) A database, stored on disk, that records configuration
and the state of all metadevices and error conditions. This information
is important to the correct operation of Solstice DiskSuiteTM software
disksets.

metainformation

(n.) Information about a resource, such as the name
of the author, the title of a document, the date of creation, and
so on. The Search Engine robot uses metainformation as well as document
contents when creating resource descriptions.

method-binding expression

(n.) An expression in the JavaServer Faces expression language that refers to a method of a backing
bean. This method performs either event handling, validation, or navigation
processing for the UI component whose tag uses the method-binding
expression.

(message handling system) (n.) A group of connected
URL mappings, their user agents,
and message stores.

MIB

(management information base) (n.) A tree-like structure
that defines the variables that the SNMP master agent can access. The MIB provides access to the HTTP
server’s network configuration, status, and statistics. Using
SNMP, you can view this information from the NMS. See also AUTH.

migration

(n.) The process of transporting data files, such
as data configuration or customization, from one version of a product
to another.

MIME

(multipurpose internet mail extensions) (n.) An emerging
standard for multimedia email and messaging. A protocol you can use
to include multimedia in email messages by appending the multimedia
file in the message.

MIME data type

(n.) MIME types control what types of multimedia files
the system supports.

mime.types file

(n.) The MIME type configuration file. This file maps
file extensions to MIME types to enable the server to determine the
type of content being requested. For example, requests for resources
with .html extensions indicate that the client
is requesting an HTML file, while requests for resources with .gif extensions indicate that the client is requesting an image
file in GIF format.

mirror node

(n.) An active HADB node that contains the same data
as another active node, but resides in the other data redundancy unit.
Each active node must have a mirror node; therefore nodes occur in
pairs. When a node detects that its mirror node has failed, it takes
over the failed node’s role and continues service. See also HADB, active node, spare node, and
data redundancy unit (DRU).

mixed-content model

(n.) A DTD specification
that defines an element as containing a mixture of text and one more
other elements. The specification must start with #PCDATA,
followed by diverse elements, and must end with the "zero-or-more"
asterisk symbol (*).

MMP

(Messaging Multiplexor) (n.) A specialized Messaging
Server that acts as a single point of connection to multiple mail
servers, facilitating the distribution of a large user base across
multiple mailbox hosts.

mobile application configuration

(n.) An Access Manager service that allows the setup
of address book, calendar, and mail applications for delivery to a
mobile device.

(n.) A transportable wireless device such as a mobile
phone or a personal digital assistant.

mobile devices link

(n.) A hypertext link appearing on the Portal Desktop.

mobile devices page

(n.) A web page which allows users to manage mobile
device options.

Mobile Portal Desktop

(n.) A Portal Desktop displayed on a mobile device.

moderator

(n.) A person who first receives all email addressed
to a mailing list in order to decide if the message should be forwarded
to the mailing list. The moderator can edit the message before forwarding
the message to the mailing list. See also mail list, expansion, member.

(2)
(n.) A group of Java Enterprise System servers dependent
on one another or closely enough related to be deployed as a unit
to provide a specific service or set of services. Service modules
are multi-server assemblies that have been pretested for use in deployment architectures.

(message transfer agent) (n.) A specialized program
for routing and delivering messages. MTAs work together to transfer
messages and deliver them to the intended recipient. The MTA determines
whether a message is delivered to the local message store or routed
to another MTA for remote delivery.

MTA configuration file

(n.) The imta.cnf file that contains
all channel definitions for the
Messaging Server as well as the rewrite rule that determine how addresses are rewritten for routing.

MTA directory cache

(n.) A snapshot of the directory service information
about users and groups required by the MTA to process messages. See
also directory synchronization

(n.) A replication model in which entries can be written
and updated on any of several master replica copies without requiring
communication with other master replicas before the write or update
is performed. Each server maintains a change log for the replica.
Modifications made on one server are automatically replicated to the
other servers. In case of conflict, a time stamp is used to determine
which server holds the most recent version.

multiplexor

(n.) The server containing the database link that
communicates with the remote server.