************************************************************************
I remember, some month ago there were questions about metamail.exe and
the mailcap file. Users also complained that the documentation of
metamail were quite scanty.
I found a sample mailcap file in a program package that is free
distributable. It's well commented and can serve as a "tutorial".
Tibor Mocsar
----- cut here ---------------------------------------------------------
# Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
#
# Permission to use, copy, modify, and distribute this material
# for any purpose and without fee is hereby granted, provided
# that the above copyright notice and this permission notice
# appear in all copies, and that the name of Bellcore not be
# used in advertising or publicity pertaining to this
# material without the specific, prior written permission
# of an authorized representative of Bellcore. BELLCORE
# MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
# OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS",
# WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
#
# Prototype Mailcap file
# Note that support for text & multipart are "built in" to metamail,
# as are rudimentary support for message, and application.
# However, any of these may be overridden in mailcap.
#
# Note that users may override or extend this with a .mailcap
# file in their own directory. However, there is NO NEED
# for them to copy entries from this file, as metamail will
# pick up entries from both the system and personal mailcap files.
#
audio/au; plany %s
image/jpeg; cshow %s+
image/gif; svga %s
image/*; showpicture %s
message/partial; showpart %s %{id} %{number} %{total}
message/external-body; showexternal %s %{access-type} %{name} %{site} %{directory} %{mode} ; needsterminal
# If you have an interactive Postscript interpreter, you should think carefully
# before replacing lpr with it in the following line, because PostScript
# can be an enormous security hole. It is RELATIVELY harmless
# when sent to the printer...
application/postscript ; lpr %s ; label="A Postscript File";\
compose="getfilename Postscript %s"
# The following should be commented out if you do NOT have atomicmail
application/atomicmail; atomicmail %s ; needsterminal
# The following give rudimentary capabilities to read old andrew format
# even to non-Andrew sites, since "ezview" comes with metamail.
x-be2; ezview %s ; copiousoutput
application/andrew-inset; ezview %s ; copiousoutput; edit=ez -d %s; compose="ez -d %s"; label="An Andrew inset/document"
# The following gives rudimentary capability for receiving
# text mail in the ISO-8859-1 character set, which covers many European
# languages, and the ISO-8859-8 character set, which includes Hebrew
# Note that the pipe to tr ensures that the "ISO" is case-insensitive.
#text/richtext; shownonascii iso-8859-8 -e richtext -p %s; test=test "`echo %{charset} | tr A-Z a-z`" = iso-8859-8; copiousoutput
#text/richtext; shownonascii iso-8859-1 -e richtext -p %s; test=test "`echo %{charset} | tr A-Z a-z`" = iso-8859-1; copiousoutput
#text/plain; shownonascii iso-8859-8 %s; test=test "`echo %{charset} | tr A-Z a-z`" = iso-8859-8; copiousoutput
text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr A-Z a-z`" = iso-8859-1; copiousoutput
text/richtext; richtext %s
# If you have Andrew at your site, you MIGHT prefer to replace the
# above line with the following one, but probably won't because
# ez takes so long to start up.
# text/richtext; richtoatk < %s | ezview - ; copiousoutput
# The following is a VERY rough cut at showing mail from Sun's openwindows mailtool
x-sun-attachment; sun-to-mime.csh %s
audio-file; sun-audio-file.csh %s
default; cat %s; copiousoutput
# The following all appear AFTER the corresponding READING entries, and
# are for use in messages composition, e.g. in the "mailto" program
audio/basic; showaudio %s; compose=audiocompose %s; edit=audiocompose %s; label="An audio fragment"
# In the three following lines, the exit 0 junk is necessary because xwd
# doesn't always exit with a valid exit status!
# Note that most sites can choose just one of these three!
image/gif; showpicture %s; compose="xwd -frame | xwdtoppm | ppmtogif > %s\; exit 0"; label="An X11 window image dump in GIF format for X11R4"
image/gif; showpicture %s; compose="xwd -frame | xwdtopnm | ppmtogif > %s\; exit 0"; label="An X11 window image dump in GIF format for X11R5"
image/x-xwd; showpicture %s; compose=xwd -frame > %s\; exit 0; label="An X11 window image dump in X-XWD format"
# The following is used for distributing metamail patches
# It should probably be used only by those administering metamail at a site.
# You will need to replace "source-tree-root" with the real root of your
# actual metamail source tree.
# You can also modify this line to get metamail patches from some trusted
# server other than thumper, if there is one -- man patch-metamail" for help.
application/x-metamail-patch;patch-metamail source-tree-root %{patchnumber}; needsterminal