1 |
edhill |
1.1 |
mpack/munpack version 1.5 for mac |
2 |
|
|
|
3 |
|
|
Mpack and munpack are utilities for encoding and decoding |
4 |
|
|
(respectively) binary files in MIME (Multipurpose Internet Mail |
5 |
|
|
Extensions) format mail messages. For compatibility with older forms |
6 |
|
|
of transferring binary files, the munpack program can also decode |
7 |
|
|
messages in split-uuencoded format. The Macintosh version can also |
8 |
|
|
decode messages in split-BinHex format. |
9 |
|
|
|
10 |
|
|
The canonical FTP site for this software is ftp.andrew.cmu.edu:pub/mpack/ |
11 |
|
|
Binaries are no longer provided. The pc, os2, amiga and archimedes ports |
12 |
|
|
have been removed. The mac version probably doesn't compile anymore, but |
13 |
|
|
is still included (MacOS X users can use the unix version...) |
14 |
|
|
|
15 |
|
|
This MIME implementation is intended to be as simple and portable as |
16 |
|
|
possible. For a slightly more sophisticated MIME implementation, see |
17 |
|
|
the program MetaMail, available via anonymous FTP to |
18 |
|
|
thumper.bellcore.com, in directory pub/nsb |
19 |
|
|
|
20 |
|
|
|
21 |
|
|
Decoding MIME messages: |
22 |
|
|
|
23 |
|
|
To decode a MIME message, first save it to a text file. If possible, |
24 |
|
|
save it with all headers included. Mpack can decode some MIME files |
25 |
|
|
when the headers are missing or incomplete, other files it cannot |
26 |
|
|
decode without having the information in the headers. In general, |
27 |
|
|
messages which have a statement at the beginning that they are in MIME |
28 |
|
|
format can be decoded without the headers. Messages which have been |
29 |
|
|
split into multiple parts generally require all headers in order to be |
30 |
|
|
reassembled and decoded. |
31 |
|
|
|
32 |
|
|
Some LAN-based mail systems and some mail providers (including America |
33 |
|
|
Online, as of the writing of this document) place the mail headers at |
34 |
|
|
the bottom of the message, instead of at the top of the message. If |
35 |
|
|
you are having problems decoding a MIME message on such a system, you |
36 |
|
|
need to convert the mail back into the standard format by removing the |
37 |
|
|
system's nonstandard headers and moving the standard Internet headers |
38 |
|
|
to the top of the message (separated from the message body with a |
39 |
|
|
blank line). |
40 |
|
|
|
41 |
|
|
There must be exactly one message per file. Mpack cannot deal with |
42 |
|
|
multiple messages in a single file, to decode things correctly it must |
43 |
|
|
know when one message ends and the next one begins. |
44 |
|
|
|
45 |
|
|
The Macintosh version of mpack/munpack is a single standalone |
46 |
|
|
application. A text file may be decoded either by drag & drop, or by |
47 |
|
|
choosing the "Decode Files..." item from the application's File menu. |
48 |
|
|
Non-text files may be encoded either by drag & drop, or by choosing |
49 |
|
|
the "Encode Files..." item from the application's File menu. |
50 |
|
|
|
51 |
|
|
The Macintosh version of mpack/munpack supports the new MacMIME |
52 |
|
|
standard (RFC 1740). This allows cross-platform transport of |
53 |
|
|
Macintosh files to any MIME-capable machine, and also preserves |
54 |
|
|
Macintosh specific file attributes between two Macintoshes. Mpack |
55 |
|
|
will use MacMIME for any unrecognized Macintosh file, and regular MIME |
56 |
|
|
for standard MIME types. |
57 |
|
|
|
58 |
|
|
For more details and descriptions of the preferences, see the "Help |
59 |
|
|
Using Mpack..." menu item in mpack which can be found under the help |
60 |
|
|
menu in systems 7 and above, and under the apple menu in older |
61 |
|
|
systems. |
62 |
|
|
|
63 |
|
|
Reporting bugs: |
64 |
|
|
|
65 |
|
|
Bugs and comments should be reported to mpack-bugs@andrew.cmu.edu. |
66 |
|
|
When reporting bugs or other problems, please include the following |
67 |
|
|
information: |
68 |
|
|
|
69 |
|
|
* The version number of Mpack |
70 |
|
|
* The platform (Unix, PC, OS/2, Mac, Amiga, Archimedes) |
71 |
|
|
* The EXACT output of any unsuccessful attempts. |
72 |
|
|
* If having a problem decoding, the first couple of lines |
73 |
|
|
of the input file. |
74 |
|
|
|
75 |
|
|
|
76 |
|
|
Compilation: |
77 |
|
|
|
78 |
|
|
Mpack was compiled with THINK C 6.0 with the 4-byte int option turned |
79 |
|
|
on (and the ANSI-small library compiled with the 4-byte int option) |
80 |
|
|
and prototype enforcement turned off. Included with this distribution |
81 |
|
|
should be the files "macproj.hqx" which is a BinHex4 version of the |
82 |
|
|
THINK C 6.0 project file, and "macrsrc.hqx" which is a BinHex4 version |
83 |
|
|
of the resources file. |
84 |
|
|
|
85 |
|
|
Mpack checks for the existence of "Internet Config", and if it is |
86 |
|
|
available, mpack uses it to translate MIME types to and from Macintosh |
87 |
|
|
type/creator codes. Included is the file "macICglue.hqx" which is a |
88 |
|
|
BinHex4 version of Internet Config's MPW object file library. This |
89 |
|
|
needs to be linked with the application. |
90 |
|
|
|
91 |
|
|
Using mpack: |
92 |
|
|
|
93 |
|
|
See the "Help Using Mpack..." menu item in the application. |
94 |
|
|
|
95 |
|
|
|
96 |
|
|
Acknowledgements: |
97 |
|
|
|
98 |
|
|
Written by John G. Myers, jgm+@cmu.edu |
99 |
|
|
|
100 |
|
|
The mac version was written by Christopher J. Newman, chrisn+@cmu.edu |
101 |
|
|
|
102 |
|
|
Send all bug reports to mpack-bugs@andrew.cmu.edu |
103 |
|
|
|
104 |
|
|
Thanks to Nathaniel Borenstein for testing early versions of mpack and |
105 |
|
|
for making many helpful suggestions. |
106 |
|
|
|
107 |
|
|
|
108 |
|
|
PGP signature: |
109 |
|
|
|
110 |
|
|
The mpack 1.6 distribution is not pgp signed. |
111 |
|
|
|
112 |
|
|
Legalese: |
113 |
|
|
|
114 |
|
|
(C) Copyright 1993,1994 by Carnegie Mellon University |
115 |
|
|
All Rights Reserved. |
116 |
|
|
|
117 |
|
|
Permission to use, copy, modify, distribute, and sell this software |
118 |
|
|
and its documentation for any purpose is hereby granted without fee, |
119 |
|
|
provided that the above copyright notice appear in all copies and that |
120 |
|
|
both that copyright notice and this permission notice appear in |
121 |
|
|
supporting documentation, and that the name of Carnegie Mellon |
122 |
|
|
University not be used in advertising or publicity pertaining to |
123 |
|
|
distribution of the software without specific, written prior |
124 |
|
|
permission. Carnegie Mellon University makes no representations about |
125 |
|
|
the suitability of this software for any purpose. It is provided "as |
126 |
|
|
is" without express or implied warranty. |
127 |
|
|
|
128 |
|
|
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO |
129 |
|
|
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY |
130 |
|
|
AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE |
131 |
|
|
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES |
132 |
|
|
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN |
133 |
|
|
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING |
134 |
|
|
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS |
135 |
|
|
SOFTWARE. |
136 |
|
|
|
137 |
|
|
Portions of this software are derived from code written by Bell |
138 |
|
|
Communications Research, Inc. (Bellcore) and by RSA Data Security, |
139 |
|
|
Inc. and bear similar copyrights and disclaimers of warranty. |
140 |
|
|
|