pInitFunc and pFunc function prototypes. These functions must be exported by the plug-in in order for it to load. For more information, see "Writing the Initialization and Plug-in Functions."GetHeaderFile and GetBodyFile functions with the 4.0 GetMessageFile function. For more information, see "Replacing Dropped 3.0 Functions."msg4plugins.h header file. You can see this file in pInitFunc function and compile against the 4.0 header file, these changes will not affect the operation of 3.0 plug-ins.
[Top]
GetMessageFile function combines two 3.0 functions, GetHeaderFile and GetBodyFile. In the 3.0 Messaging Server Plug-in API, these two functions were used to find, open, and rewrite or encode the header and body files of the message:
char *GetHeaderFile (Message *pMessage);
char *GetBodyFile (Message *pMessage);In the Messaging Server Plug-in API, the header and body portions of the message are in the same file. The functions returned the full path name to the file that contained the RFC 822 header and RFC 822 body portions of the message. To convert your 3.0 plug-in for use in the 4.0 Messaging Server, use the
GetMessageFile function in place of the two 3.0 functions.
char *GetMessageFile (Message *pMessage);This function returns the filename and path of the message file, which includes the header and body portions of the message. Your plug-in will need to read the message file and parse the header and body itself. For an example that shows how to use
GetMessageFile, see "Get the message file."
[Top]
Last Updated: 11/19/98 10:24:13
[an error occurred while processing this directive]