Penguin
Recent Changes
Annotated edit history of mailcap(5) version 4, including all changes. View license author blame.
Rev Author # Line
1 perry 1 MAILCAP
2 !!!MAILCAP
3 NAME
4 DESCRIPTION
5 BUILT-IN CONTENT-TYPE SUPPORT
6 FILES
7 SEE ALSO
8 COPYRIGHT
9 AUTHOR
10 ----
11 !!NAME
12
13
14 mailcap - metamail capabilities file
15 !!DESCRIPTION
16
17
18 The ''mailcap'' file is read by the ''metamail''
19 program to determine how to display non-text at the local
20 site.
21
22
23 The syntax of a mailcap file is quite simple, at least
24 compared to termcap files. Any line that starts with
25
26
27 Each individual mailcap entry consists of a content-type
28 specification, a command to execute, and (possibly) a set of
29 optional
30
31
32 text/plain; cat %s
33
34
35 The optional flags can be used to specify additional
36 information about the mail-handling command. For
37 example:
38
39
40 text/plain; cat %s; copiousoutput
41
42
43 can be used to indicate that the output of the 'cat' command
44 may be voluminous, requiring either a scrolling window, a
45 pager, or some other appropriate coping
46 mechanism.
47
48
49 The
50
51
52 The
53
54
55 If no
56
57
58 Two special codes can appear in the viewing command for
59 objects of type multipart (any subtype). These are
60
61
62 The
63
64
65 The
66
67
68 The
69
70
71 The
72
73
74 The
75
76
77 The
78
79
80 __needsterminal__
81
82
83 If this flag is given, the named interpreter needs to
84 interact with the user on a terminal. In some environments
85 (e.g. a window-oriented mail reader under X11) this will
86 require the creation of a new terminal emulation window,
87 while in most environments it will not. If the mailcap entry
88 specifies
89
90
91 __copiousoutput__
92
93
94 This flag should be given whenever the interpreter is
95 capable of producing more than a few lines of output on
96 stdout, and does no interaction with the user. If the
97 mailcap entry specifies copiousoutput, and pagination has
98 been requested via the
99 !!BUILT-IN CONTENT-TYPE SUPPORT
100
101
102 The metamail program has built-in support for a few key
103 content-types. In particular, it supports the text type, the
104 multipart and multipart/alternative type, and the
105 message/rfc822 types. This support is incomplete for many
106 subtypes -- for example, it only supports US-ASCII text in
107 general. This kind of built-in support can be OVERRIDDEN by
108 an entry in any mailcap file on the user's search path.
109 Metamail also has rudimentary built-in support for types
110 that are totally unrecognized -- i.e. for which no mailcap
111 entry or built-in handler exists. For such unrecognized
112 types, metamail will write a file with a
113 !!FILES
114
115
116 $HOME/.mailcap:/etc/mailcap:/usr/share/etc/mailcap:/usr/local/etc/mailcap
117 -- default path for mailcap files.
118 !!SEE ALSO
119
120
4 perry 121 run-mailcap(1)__, mailcap.order__(5)__,
1 perry 122 update-mime__(8)
123 !!COPYRIGHT
124
125
126 Copyright (c) 1991 Bell Communications Research, Inc.
127 (Bellcore)
128
129
130 Permission to use, copy, modify, and distribute this
131 material for any purpose and without fee is hereby granted,
132 provided that the above copyright notice and this permission
133 notice appear in all copies, and that the name of Bellcore
134 not be used in advertising or publicity pertaining to this
135 material without the specific, prior written permission of
136 an authorized representative of Bellcore. BELLCORE MAKES NO
137 REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY OF THIS
138 MATERIAL FOR ANY PURPOSE. IT IS PROVIDED
139 !!AUTHOR
140
141
142 Nathaniel S. Borenstein
143 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.