1
# This is a sample mailcap file based on the sample mailcap file
2
# contained in the metamail distribution (version 2.7) from Bellcore.
3
# This sample is for a Unix system. Look at the original sample from
4
# the metamail distribution for more ideas. This is a simplified version
5
# to explain how it works with Pine. As of October, 1994, metamail was
6
# available via anonymous ftp from the host thumper.bellcore.com in the
7
# file /pub/nsb/mm2.7.tar.Z.
10
# Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
12
# Permission to use, copy, modify, and distribute this material
13
# for any purpose and without fee is hereby granted, provided
14
# that the above copyright notice and this permission notice
15
# appear in all copies, and that the name of Bellcore not be
16
# used in advertising or publicity pertaining to this
17
# material without the specific, prior written permission
18
# of an authorized representative of Bellcore. BELLCORE
19
# MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
20
# OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS",
21
# WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
23
# The mailcap viewers are used by Pine when viewing pieces of a message
24
# from within the attachment viewer. That is, you type the "V" command
25
# when already viewing a message.
27
# Pine expects the mailcap file to be in /etc/mailcap on Unix systems.
28
# Users may override or extend this with a .mailcap file in their home
29
# directory. The contents of that will be combined with /etc/mailcap.
30
# Users may override this standard Pine mailcap path
31
# ("~/.mailcap:/etc/mailcap") by defining the environment variable
32
# MAILCAPS to be equal to the colon separated path.
34
# On PC's (DOS or Windows) the file MAILCAP is searched for first in the
35
# same directory where the user's PINERC is located and then in the same
36
# directory where PINE.EXE is located. The first would be the user's personal
37
# override file and the second the common file used by all users. Users
38
# may override this location by defining the environment variable MAILCAPS
39
# to be equal to the *semicolon* separated path.
41
# Pine does not use the "compose=" portion of mailcap entries (and doesn't
42
# provide a general method of composing different types of messages).
43
# Pine doesn't pay attention to "copiousoutput", but always pipes the output
44
# to its standard scrolling text window if "needsterminal" is not set.
45
# If "needsterminal" is set, then Pine sets the terminal or terminal window
46
# back to the state it was in when Pine was started and lets the viewer run.
47
# When the viewer finishes, Pine resets the terminal and redraws the screen.
48
# If any user interaction with the viewer is required and the viewer runs
49
# in the same terminal window as Pine, then "needsterminal" should be set.
50
# The "test=" commands are used as defined in RFC1524, except that the
51
# data file is not available to the test command.
53
# Since mailcap is only used from the attachment viewer, the message being
54
# viewed will always be a single part, so "multipart" entries in mailcap have
55
# no effect on Pine. Type "text/plain" with "charset=usascii" or charset
56
# matching the character-set variable are intercepted and displayed by Pine
57
# in the normal way, not displayed by a mailcap viewer. Besides those
58
# exceptions just listed, all other types and subtypes are subject to
59
# being displayed by a mailcap viewer. If no match is found for types text
60
# or message, Pine will display them in its usual way.
62
# As a special case, the "image-viewer" variable from the pinerc file is
63
# supported as if an extra entry for type image/* came first in the
64
# personal mailcap file. That's for backwards compatibility.
67
# The following line causes the xv program to be used to display all
68
# image types if the DISPLAY variable is set (indicating the user is
69
# using X). (xv is written by John Bradley, bradley@cis.upenn.edu. There
70
# are also other X image viewer programs you could use, such as xloadimage.)
71
image/*; xv %s; test=test -n "$DISPLAY"
73
# The effect of the following is to send ALL audio subtypes to the
74
# showaudio program. If possible, it would be desirable to also include
75
# a test command that could decide whether or not the user could play audio.
76
# That would be something like "test=can_do_audio %t". (Showaudio is a shell
77
# script included in the metamail distribution.)
80
# (Showexternal is a shell script included in the metamail distribution.)
81
message/external-body; showexternal %s %{access-type} %{name} \
82
%{site} %{directory} %{mode} %{server}; \
83
needsterminal; composetyped = extcompose %s; \
84
description="A reference to data stored in an external location"
86
# If you have an interactive Postscript interpreter, you should think carefully
87
# before replacing lpr with it in the following line, because PostScript
88
# can be an enormous security hole. It is RELATIVELY harmless
89
# when sent to the printer...
90
application/postscript ; lpr %s \; echo SENT FILE TO PRINTER ;\
91
description="A Postscript File";
93
#application/postscript; gspreview %s ; test=test -n "$DISPLAY"
95
# The following gives rudimentary capability for receiving
96
# text mail in the ISO-8859-1 character set, which covers many European
97
# languages, and the ISO-8859-8 character set, which includes Hebrew
98
# Note that the pipe to tr ensures that the "ISO" is case-insensitive.
99
# (This is also from metamail.)
101
#### However, they are commented out here as they use a "test" method
102
#### that can cause malicious data in the message's charset parameter
103
#### to get executed. A better alternative would be to replace the "test"
104
#### command with a script that does a safer case-insensitive comparison.
105
#text/plain; shownonascii iso-8859-8 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8 -a -n "$DISPLAY" ; copiousoutput
106
#text/plain; shownonascii iso-8859-8 %s | more ; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-8; needsterminal
107
#text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1 -a -n "$DISPLAY" ; copiousoutput
108
#text/plain; shownonascii iso-8859-1 %s | more ; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1 ; needsterminal
110
# The following displays Japanese text at sites where
111
# the "kterm" program is installed:
112
#text/plain; kterm -geometry +0+0 -e more %s /dev/null; \
113
test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-2022-jp
115
# This maps MPEG video data to the viewer 'mpeg_play'.
116
# (Mpeg_play is part of the MPEG distribution from The Berkeley Plateau
117
# Research Group and is available via anonymous ftp from toe.cs.berkeley.edu.)
118
video/mpeg; mpeg_play %s ; test=test -n "$DISPLAY"
120
# This maps all other types of video to the xanim viewer. (Xanim is written
121
# by Mark Podlipec, podlipec@wellfleet.com.)
122
video/*; xanim %s ; test=test -n "$DISPLAY"
124
# The xdvi program display TeX dvi files on an X server.
125
application/x-dvi; xdvi %s ; test=test -n "$DISPLAY"
127
# Type octet-stream (binary) data can be displayed as a hex dump before
128
# you decide whether or not you want to save it to a file. (Hd is just
129
# a standard hex dump program. You could use "od" if you don't have an
130
# "hd". Naive users may find the output from this entry confusing.)
131
application/octet-stream; hd; copiousoutput; description="Hex dump of data"