1# Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
2#
3# Permission to use, copy, modify, and distribute this material
4# for any purpose and without fee is hereby granted, provided
5# that the above copyright notice and this permission notice
6# appear in all copies, and that the name of Bellcore not be
7# used in advertising or publicity pertaining to this
8# material without the specific, prior written permission
9# of an authorized representative of Bellcore.  BELLCORE
10# MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
11# OF THIS MATERIAL FOR ANY PURPOSE.  IT IS PROVIDED "AS IS",
12# WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
13#
14# Prototype Mailcap file
15# Note that support for text & multipart are "built in" to metamail,
16# as are rudimentary support for message, and application.
17# However, any of these may be overridden in mailcap.
18#
19# Note that users may override or extend this with a .mailcap
20# file in their own directory.  However, there is NO NEED
21# for them to copy entries from this file, as metamail will
22# pick up entries from both the system and personal mailcap files.
23#
24# Note that the effect of the following is to send ALL audio subtypes to the
25# showaudio program, but to compose audio (e.g. in the mailto program)
26# using "audio/basic" as the type.
27audio/*; showaudio %s
28audio/basic; showaudio %s; compose=audiocompose %s; edit=audiocompose %s; description="An audio fragment"
29
30# The following line is for sites where xv understands jpeg but xloadimage is preferred.
31image/jpeg; showpicture -viewer xv %s
32# The following sends all other image subtypes to showpicture.
33image/*; showpicture %s
34# The following all appear AFTER the corresponding READING entries, and
35# are for use in messages composition, e.g. in the "mailto" program
36# In the following lines, the exit 0 junk is necessary because xwd
37# doesn't always exit with a valid exit status!
38# For sites with current (X11R5) pbm utilities
39image/gif; showpicture %s; compose="xwd -frame | xwdtopnm | ppmtogif > %s\; exit 0"; description="An X11 window image dump in GIF format"
40# The following line should be used instead of the previous by sites
41# with old (X11R4) pbm utilities
42#image/gif; showpicture %s; compose="xwd -frame | xwdtoppm | ppmtogif > %s\; exit 0"; description="An X11 window image dump in GIF format"
43# For receiving X11 window image dumps from older versions of Andrew messages
44image/x-xwd; showpicture %s; description="An X11 window image dump in X-XWD format"
45
46message/partial; showpartial %s %{id} %{number} %{total}
47message/external-body; showexternal %s %{access-type} %{name} %{site} %{directory} %{mode} %{server}; \
48	needsterminal; composetyped = extcompose %s; \
49	description="A reference to data stored in an external location"
50
51# You can alter the above entry to only use certain access-types by
52# adding a clause like the following before the "description=" line:
53#	test=test %{access-type}  = mail-server;  \
54
55
56# If you have an interactive Postscript interpreter, you should think carefully
57# before replacing lpr with it in the following line, because PostScript
58# can be an enormous security hole.  It is RELATIVELY harmless
59# when sent to the printer...
60application/postscript ; lpr %s \; echo SENT FILE TO PRINTER ; description="A Postscript File";\
61	compose="getfilename Postscript %s"
62
63# The following should be commented out if you do NOT have safe-tcl
64# and should be uncommented if you DO have safe-tcl
65#multipart/enabled-mail; show-enabled %F
66#application/safe-tcl; swish -safe -messaging -f %s
67
68# The following should be commented out if you do NOT have atomicmail
69# and should be uncommented if you DO have ATOMICMAIL
70#application/atomicmail; atomicmail %s; compose=surveyor.am -p %s; description="An interactive ATOMICMAIL survey"
71# The following should be used instead if you have atomicmail but not TK.
72#application/atomicmail; atomicmail %s ; needsterminal
73#application/atomicmail; atomicmail %s; compose=surveyor.am -p %s; description="An interactive ATOMICMAIL survey"; needsterminal
74
75# The following give rudimentary capabilities to read old andrew format
76# even to non-Andrew sites, since "ezview" comes with metamail.
77x-be2;     ezview %s ; copiousoutput
78application/andrew-inset;     ezview %s ; copiousoutput; edit=ez -d %s; compose="ez -d %s"; description="An Andrew inset/document"
79
80# The following gives rudimentary capability for receiving
81# text mail in the ISO-8859-1 character set, which covers many European
82# languages, and the ISO-8859-8 character set, which includes Hebrew
83# Note that the pipe to tr ensures that the "ISO" is case-insensitive.
84text/richtext; shownonascii iso-8859-8 -e richtext -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`"  = iso-8859-8; copiousoutput
85text/richtext; shownonascii iso-8859-1 -e richtext -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`"  = iso-8859-1; copiousoutput
86text/plain; shownonascii iso-8859-8 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8; copiousoutput
87text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput
88text/enriched; shownonascii iso-8859-8 -e richtext -e -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`"  = iso-8859-8; copiousoutput
89text/enriched; shownonascii iso-8859-1 -e richtext -e -p %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`"  = iso-8859-1; copiousoutput
90
91# The following displays Japanese text at sites where the "kterm" program is installed:
92text/plain; kterm -geometry +0+0  -e more %s /dev/null; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-2022-jp
93
94
95text/richtext; richtext %s; copiousoutput
96# If you have Andrew at your site, you MIGHT prefer to replace the
97# above line with the following one, but probably won't because
98# ez takes so long to start up.
99# text/richtext; richtoatk < %s | ezview - ; copiousoutput
100text/enriched; richtext -e %s; copiousoutput
101
102# The following is a VERY rough cut at showing mail from Sun's openwindows mailtool
103# Old version
104# x-sun-attachment; sun-to-mime %s
105x-sun-attachment; sun2mime %s
106audio-file; sun-audio-file %s
107postscript-file; lpr %s \; echo SENT FILE TO PRINTER
108default; sun-message.csh %s %{encoding}; needsterminal
109mail-file; sun-message.csh %s %{encoding}; needsterminal
110sun-deskset-message; sun-message.csh %s %{encoding}; needsterminal
111
112# The following is used for distributing metamail patches
113# It should probably be used only by those administering metamail at a site.
114# You will need to replace "source-tree-root" with the real root of your
115# actual metamail source tree.
116# You can also modify this line to get metamail patches from some trusted
117# server other than thumper, if there is one -- man patch-metamail" for help.
118application/x-metamail-patch; cat %s > /dev/null \; patch-metamail source-tree-root %{patchnumber}; needsterminal
119
120# The following is for support of MacMIME, especially those
121# the Columbia AppleTalk package (CAP) installed.
122# For more info about MacMIME, send email to paf@nada.kth.se
123#
124# If you don't have CAP, and haven't changed rcvAppleSingle
125# or sndAppleSingle, you should comment out this line.
126application/applefile; rcvAppleSingle %s; compose="sndAppleSingle %s";description="An Apple Macintosh file in AppleSingle format"
127
128#
129# The following is for interoperability with Z-Mail version 3.0 and beyond.
130# To enable this compatibility, uncomment all of the following lines.
131#
132# For more info about Z-Mail, send email to info@z-code.com
133#
134#application/x-movie; movieplayer %s; compose=moviemaker %s; \
135#       description="Movie"; \
136#        x11-bitmap="/usr/lib/Zmail/bitmaps/movie.xbm"
137#application/x-inventor; examine %s; description="Inventor file"; \
138#        x11-bitmap="/usr/lib/Zmail/bitmaps/inventor.xbm"
139#application/x-zm-fax; zfax %s; description="Z-Fax document"; \
140#	x11-bitmap="/usr/lib/Zmail/bitmaps/fax.xbm"
141#application/x-showcase; showcase %s; compose=showcase %s; \
142#	description="Showcase document"; \
143#	x11-bitmap="/usr/lib/Zmail/bitmaps/showcase.xbm"
144#application/x-jot; jot %s; compose=jot %s; description="Jot document"; \
145#	x11-bitmap="/usr/lib/Zmail/bitmaps/jot.xbm"
146#image/x-sgi; ipaste %s; compose=imgworks %s; description="SGI image"; \
147#	x11-bitmap="/usr/lib/Zmail/bitmaps/image.xbm"
148#audio/x-aiff; playaiff %s; compose=recordaiff -t 60 %s;	\
149#	description="AIFF Audio"; x11-bitmap="/usr/lib/Zmail/bitmaps/sound.xbm"
150#image/x-bitmap; bitmap %s; description="X11 bitmap"; \
151#	x11-bitmap="/usr/lib/Zmail/bitmaps/bitmap.xbm"
152#image/x-xpm1; olpixmap %s; description="OL pixmap"; \
153#	x11-bitmap="/usr/lib/Zmail/bitmaps/bitmap.xbm"
154#application/x-island-write; IslandWrite %s; compose=IslandWrite %s; \
155#	description="IslandWrite document"; \
156#	x11-bitmap="/usr/lib/Zmail/bitmaps/islwrite.xbm"
157#application/x-island-draw; IslandDraw %s; compose=IslandDraw %s; \
158#	description="IslandDraw document"; \
159#	x11-bitmap="/usr/lib/Zmail/bitmaps/isldraw.xbm"
160#application/x-island-paint; IslandPaint %s; compose=IslandPaint %s; \
161#	description="IslandPaint document"; \
162#	x11-bitmap="/usr/lib/Zmail/bitmaps/islpaint.xbm"
163#application/x-framemaker; maker -f %s; compose=maker -f %s; \
164#	description="FrameMaker document"; \
165#	x11-bitmap="/usr/lib/Zmail/bitmaps/frame.xbm"
166#application/x-wingz; Wingz %s; compose=Wingz %s; \
167#	description="Wingz document"; \
168#	x11-bitmap="/usr/lib/Zmail/bitmaps/wingz.xbm"
169# Old Z-mail format
170#x-zm-multipart: sun-to-mime %s
171
172#Another suggested way to use FrameMaker
173# application/x-framemaker; clclient -f %s \; sleep 60 ; \
174#	compose="getfilename FrameMaker %s"
175
176# A common problem with the mailcap mechanism is getting differential
177# behavior from different programs.  This problem is compounded by the fact
178# that some programs, notably Mosaic, do not implement the "test" clause in
179# mailcap files.  The following two mailcap entries should give you a model
180# for a hack that will allow you to get differential behavior from Mosaic and
181# metamail in spite of this fact.  It exploits the fact that metamail always
182# sets the MM_MAILER variable (if only to "unknown") while Mosaic does not.
183#
184# foo/bar; echo mosaic; test=test "$MM_MAILER" = ""
185# foo/bar; echo not mosaic
186