XFOR: GroupWise Connector Fails to Deliver Mail with Two or More AttachmentsID: Q234585
|
When a Novell GroupWise 4.x user sends a mail message with two or more file attachments to an Exchange Server user, the message may not be delivered. Upon investigation, the message has moved to the GroupWise API Gateway's Gwprob directory.
The GroupWise API gateway malforms the API file when the Convert Attachments option in the GroupWise Administrator is selected. The GroupWise API gateway malforms the ATTACH-FILE section of the API file it creates by placing a comma at the end of the "-CONVERSION-ALLOWED-" keyword. It should use a semi-colon. According to the GroupWise API documentation, the comma it places at the end of the "-CONVERSION-ALLOWED-" key word is illegal. Subsequent processing of this malformed API file by the API gateway reports that the keyword is unrecognized, and the message is then moved to the groupwise domain\Wpgate\Api\Gwprob folder.
Clear the Convert Attachments option in the GroupWise Administrator. To do so:
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.
The Convert Attachments option is not needed to send attachments from GroupWise to Exchange Server. However, there may be a compelling reason to have this turned on. It is the responsibility of the GroupWise administrator to make any decisions about having this option turned on or off.
The problem is caused by the GroupWise API gateway, meaning the malformation in the API file is caused by the GroupWise API gateway as it is converting the GroupWise message.
Additional query words: API_IN API_OUT groupwise
Keywords : exc55
Version : winnt:5.5
Platform : winnt
Issue type : kbprb
Last Reviewed: July 6, 1999