Novell GROUPWISE 8 - ADMINISTRATION Administration Manual page 749

Because MIME handles such a variety of file types, you might need to customize aspects of MIME
for your users.
"Customizing MIME Preamble Text" on page 749
"Customizing MIME Content-Type Mappings" on page 749
Customizing MIME Preamble Text
An ASCII file called
preamble.txt
( ). This file, which is included with any MIME multipart message, is
domain\wpgate\gwia
displayed when the message recipient lacks a MIME-compliant mail reader.
The content of the
preamble.txt
format. If the recipient cannot read the message, he or she needs to either use a MIME-compliant
mail reader or reply to the sender and request the message not be sent in MIME format.
We recommend that you use the
from your GroupWise system and who lack MIME-compliant mail readers can understand why they
cannot read the message and can take corrective action.
If you choose to modify the
The maximum file size is 1024 bytes (1 KB)
This file is read by the Internet Agent when the Internet Agent starts, so if you change the file,
you must restart the Internet Agent.
The Internet Agent's gateway directory also contains a
includes the text of
preamble.txt
users will be sending mail to non-English speaking users, you might want to copy the appropriate
language sections from the
The 1024-byte limit on the size of the
does not exceed 1024 bytes.
Customizing MIME Content-Type Mappings
By default, the GroupWise client determines the MIME content-type and encoding for message
attachments. If, for some reason, the GroupWise client cannot determine the appropriate MIME
content-type and encoding for an attachment, the Internet Agent must determine the content-type
and encoding.
The Internet Agent uses a
types. Based on an attachment's content type, the Internet Agent encodes the attachment using
quoted-printable, Base64, or BinHex. Generally, quoted-printable is used for text-based files,
Base64 for application files, and BinHex for Macintosh files.
The file includes mappings for many standard files. If necessary, you can modify the
mimetype.cfg
file to include additional mappings. If an attachment is sent which does not have a mapping in the
file, the Internet Agent chooses quoted-printable, BinHex or Base64 encoding.
The file is also used for RFC-822 attachments, but UUencode or BinHex encoding
mimetype.cfg
is used regardless of the mapped content type.
is installed in the Internet Agent gateway directory
file is a warning, in English, that the file is being sent in MIME
t file so that those who read MIME messages coming
preamble.tx
file, be aware of the following considerations:
preamble.txt
translated into several languages. If you anticipate that your
file to the preamble.txt file.
preamble.all
preamble.txt
file to map attachments to the appropriate MIME content
mimetype.cfg
file. The
preamble.all
file still applies, so make sure that the file
Configuring Internet Services 749
file
preamble.all