XCLN: How to Not Convert Outbound Attachments to MacBinaryLast reviewed: July 15, 1997Article ID: Q166564 |
The information in this article applies to:
SYMPTOMSUsers and administrators of the Microsoft Exchange Macintosh client version 5.0 Service Pack 1 (SP1) have the ability to edit the Exchange Preferences file to declare which Macintosh file types will not be encoded to MacBinary. This ability will be useful to users and administrators who want to send attachments to clients other than Microsoft Exchange Client.
CAUSEBefore the release of the Microsoft Exchange Macintosh client 5.0 SP1, administrators with X.400 gateways could not properly send files from the Macintosh client because there is no specified mechanism for transporting Macintosh file types via X.400. In addition, Microsoft has been asked to address requests from organizations asking for the ability to send specific Macintosh File/Creator pairs as a data fork only. This ability takes the form of editing a new string ID in the Exchange Preferences file, ID #134, "Windows File Types." An editor such as ResEdit will be required. NOTE: ResEdit can manipulate resources crucial to the running of a Macintosh application. Users and administrators should run the Command-D keystroke combination against the Exchange Preferences file to create a copy for safekeeping. To add a global extension that will always be excluded from MacBinary Conversion (in this example, ResEdit is used):
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Keywords : kbbug5.00 kbfix5.00.sp1 kbusage XCLN
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |