Translating Messages Using a Translation Framework
Translating Messages Using a Translation Framework
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. At some point during the processing of incoming or outgoing messages, the gateway must call the message translation framework to translate the message to the appropriate format. Typically, this happens after the gateway determines that it can process the message. Most gateways do some minimal verification of the input message before calling the translation framework. For example, the gateway might verify that it can parse the destination address. If it determines that it cannot process a message, the gateway can reject the message and return an error report without ever calling the translation framework.
The gateway program calls the translation framework using the functions in the following table:
| Function | Action | When called |
|---|---|---|
| HrCnvInitGlobals | Initializes common data areas. | When the gateway starts. |
| HrCnvInitInstance | Creates a new instance of the translation framework. Each instance is single-threaded. Multiple instances can be used in separate threads. | When a new thread is created to perform translations. |
| HrCnvConvert | Performs a conversion. | When each message is translated. |
| HrCnvUninitInstance | Disposes of a previously allocated translation framework instance. | When a translation thread exits. |
The gateway should return a nondelivery report to the sender of the message if HrCnvConvert returns an error, or if the gateway cannot convert the message for another reason.
The following topic provides information about translating attachments with the HrCnvConvert function:
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.