Introduction
[Contents] [Previous] [Next] [Index]
This chapter describes messages, lists the stages involved in message processing, and explains what you can and cannot do with the Messaging Server.
Messages and Message Processing Steps
To process a message, each application goes through a sequence of steps. Each step is implemented by an executable program called a module, which the dispatcher program spawns in sequence to carry out message processing tasks. The sequence of tasks varies depending on message type.
A single message is made up of control, header, and body files.
The control, header, and body files of the message make up the key input to the module. The module can do one of two things. It can either use this input, along with the user and module databases, to generate one or more messages for further processing, or it can pass the responsibility for the message on to another Message Transfer Agent (MTA). Finally, it delivers the message to the mailbox of one of the users or bounces it.
NOTE:
For details about the parts of a message, see RFC822: "Standard for the Format
of IRD and Internet Text Message." §
[Top]
How You Can Use the Messaging Server Plug-in API
The Netscape Messaging Server 3.0 plug-in interface allows third party developers to plug in site-specific functionality. Here's what you can do with the Messaging Server Plug-in API:
Here's what you cannot do with the plug-in API:
[Top]
[Contents] [Previous] [Next] [Index]
Last Updated: 10/01/97 15:03:45
Copyright © 1997
Netscape Communications Corporation