Commit 70449531 authored by Martin Schulze's avatar Martin Schulze

git-debimport mime-support_3.18-1.3.tar.gz

parent 1059cfca
#! /bin/sh -e
if [ "$1" = "configure" ]; then
if [ -d /usr/doc -a ! -e /usr/doc/mime-support -a -d /usr/share/doc/mime-support ]; then
ln -sf ../share/doc/mime-support /usr/doc/mime-support
fi
fi
# Remove the old status directory
if [ ! -e
rm -rf /var/lib/mime
# Run the update program
if [ -x /usr/sbin/update-mime ]; then
update-mime
fi
mime-support (3.9-1.3) oldstable-security; urgency=high
mime-support (3.18-1.3) stable-security; urgency=high
* Non-maintainer upload by the Security Team
* Added patch by Florian Zumbiehl <florz@gmx.de> to fix shell character
expansion finally.
-- Martin Schulze <joey@infodrom.org> Wed, 30 Apr 2003 17:30:33 +0200
-- Martin Schulze <joey@infodrom.org> Fri, 25 Apr 2003 16:17:48 +0200
mime-support (3.9-1.2) oldstable-security; urgency=high
mime-support (3.18-1.2) stable-security; urgency=high
* Non-maintainer upload by the Security Team
* Corrected the patch against shell character expansion bugs by copying
the contents into a temporary file
-- Martin Schulze <joey@infodrom.org> Wed, 23 Apr 2003 15:19:53 +0200
-- Martin Schulze <joey@infodrom.org> Wed, 23 Apr 2003 15:17:09 +0200
mime-support (3.9-1.1) oldstable-security; urgency=high
mime-support (3.18-1.1) stable-security; urgency=high
* Non-maintainer upload by the Security Team
* Fixed insecure temporary file usage when reading from stdin (patch by
Colin Phipps)
* Fixed insecure temporary file usage when decoding a file (patch by
Colin Phipps)
* Added workaround against shell character expansion bugs by copying the
contents into a temporary file (patch by myself)
-- Martin Schulze <joey@infodrom.org> Mon, 7 Apr 2003 19:13:05 +0200
-- Martin Schulze <joey@infodrom.org> Mon, 7 Apr 2003 19:17:34 +0200
mime-support (3.18-1) unstable; urgency=high
* yet more new mime types
-- Brian White <bcwhite@pobox.com> Tue, 9 Apr 2002 23:28:49 -0400
mime-support (3.17-1) unstable; urgency=high
* fixed bug in run-mailcap v3.16-1 (closes: #141638)
-- Brian White <bcwhite@pobox.com> Sun, 7 Apr 2002 13:18:42 -0400
mime-support (3.16-1) unstable; urgency=high
* added new mime types (closes: #139333, #140539)
* brought in "mailcap" man page and fixed type (closes: #139989)
-- Brian White <bcwhite@pobox.com> Fri, 5 Apr 2002 20:44:20 -0500
mime-support (3.15-1) unstable; urgency=high
* fixed problem with saving stdin (closes: #137024)
* merged in many new types from Apache source
-- Brian White <bcwhite@pobox.com> Tue, 12 Mar 2002 20:18:19 -0500
mime-support (3.14-1) unstable; urgency=high
* added new mime types (closes: #124223, #128017, #129553, #130523)
* added more descriptive error message when no rules pass their tests
-- Brian White <bcwhite@pobox.com> Thu, 31 Jan 2002 23:07:38 -0500
mime-support (3.13-3) unstable; urgency=high
* changed urgency to get it in to testing before the base freeze
-- Brian White <bcwhite@pobox.com> Sat, 1 Dec 2001 11:30:13 -0500
mime-support (3.13-2) unstable; urgency=low
* removed debug flag from "update-mime" (oops)
-- Brian White <bcwhite@pobox.com> Fri, 30 Nov 2001 08:11:43 -0500
mime-support (3.13-1) unstable; urgency=low
* added new mime.type entries (closes: #111986, #118680, #116672)
* fixed /tmp race coditions and other problems (closes: #94869)
* /etc/mailcap is no longer a conffile (closes: #34294, #115401, #110594)
* fixed ordering within a priority when wildcards are used
-- Brian White <bcwhite@pobox.com> Fri, 30 Nov 2001 00:39:16 -0500
mime-support (3.12-1) unstable; urgency=low
* added new mime.type entries (closes: 100132, 101386, 101465)
* run update-mime during postinst (closes: 107540)
* added new mime.type entries (closes: 85028, 85395, 99117, 101386)
* remove obsolete /var/lib directory (closes: 95563)
-- Brian White <bcwhite@pobox.com> Thu, 9 Aug 2001 23:04:02 -0400
mime-support (3.11-1) unstable; urgency=low
* support escaped percent signs
* added new mime.type entries (closes: 85395, 99117)
-- Brian White <bcwhite@pobox.com> Sun, 22 Apr 2001 11:43:03 -0400
mime-support (3.10-1) unstable; urgency=low
* added "wml" mime types (closes: 69163)
* updated to new rfc-2046 (closes: 79431)
* use "x-terminal-emulator" instead of "xterm" (closes: 79788)
* set "text/css" for ".css" extensions (closes: 80281)
* changed excel and powerpoint entries (closes: 52379)
* no longer use old install-mime (closes: 69494)
* minor documentation fix (closes: 75928)
* support escaped semi-colons (closes: 76583)
* added numerous new mime.type entries
-- Brian White <bcwhite@pobox.com> Sat, 13 Jan 2001 22:42:21 -0500
mime-support (3.9-1) unstable; urgency=low
* made temp file namesunique (Bug#50576)
* made temp file names unique (Bug#50576)
* fixed problem with decoded file not being removed
-- Brian White <bcwhite@pobox.com> Thu, 18 Nov 1999 21:35:56 -0500
......
/etc/mime.types
/etc/mailcap
/etc/mailcap.order
/var/lib/mime/mime-db
/var/lib/mime/mime-support-compat
......@@ -2,11 +2,12 @@ Source: mime-support
Section: net
Priority: standard
Maintainer: Brian White <bcwhite@pobox.com>
Standards-Version: 2.4.1.0
Standards-Version: 3.1.1.1
Package: mime-support
Architecture: all
Conflicts: a2ps(<<4.10.4)
Conflicts: a2ps(<<4.10.4), metamail(<<2.7-44)
Recommends: file(>=3.27-3)
Description: MIME files 'mime.types' & 'mailcap', and support programs
As these files can be used by all MIME compliant programs, they
have been moved into their own package that others can depend upon.
......
#! /bin/sh -e
# Remove old mime stuff
install-mime --remove --package=mime-support --noparmcheck
if [ "$1" = "configure" ]; then
if [ -d /usr/doc -a ! -e /usr/doc/mime-support -a -d /usr/share/doc/mime-support ]; then
ln -sf ../share/doc/mime-support /usr/doc/mime-support
fi
fi
# Remove test-hack directory
rm -rf /var/lib/mime/tests
# Remove the old status directory (and any orphaned install-mime program)
rm -fr /var/lib/mime
rm -f /usr/sbin/install-mime
# Run the update program
if [ -x /usr/sbin/update-mime ]; then
update-mime
fi
#! /bin/sh
#
# prerm file for mime-support
if [ \( "$1" = "upgrade" -o "$1" = "remove" \) -a -L /usr/doc/mime-support ]; then
rm -f /usr/doc/mime-support
fi
if [ "$1" = "remove" ]; then
rm -f /etc/mailcap
fi
......@@ -24,48 +24,42 @@ binary-indep:
test -f debian/rules
test root = "`whoami`"
-rm -rf debian/tmp
mkdir -p debian/tmp/DEBIAN debian/tmp/etc debian/tmp/var/lib/mime debian/tmp/usr/lib/mime/packages
mkdir -p debian/tmp/usr/doc/$(package) debian/tmp/usr/sbin debian/tmp/usr/bin
mkdir -p debian/tmp/usr/man/man1 debian/tmp/usr/man/man5 debian/tmp/usr/man/man8
mkdir -p debian/tmp/DEBIAN debian/tmp/etc debian/tmp/usr/lib/mime/packages
mkdir -p debian/tmp/usr/share/doc/$(package) debian/tmp/usr/sbin debian/tmp/usr/bin
mkdir -p debian/tmp/usr/share/man/man1 debian/tmp/usr/share/man/man5 debian/tmp/usr/share/man/man8
chmod -R 755 debian/tmp
install -m 644 mime.types debian/tmp/etc/
install -m 644 mailcap debian/tmp/etc/
install -m 644 mailcap debian/tmp/usr/lib/mime/
install -m 644 mailcap.order debian/tmp/etc/
install -m 644 mailcap.order.man debian/tmp/usr/man/man5/mailcap.order.5
install -m 755 install-mime debian/tmp/usr/sbin/
install -m 644 install-mime.man debian/tmp/usr/man/man8/install-mime.8
install -m 644 mailcap.man debian/tmp/usr/share/man/man5/mailcap.5
install -m 644 mailcap.order.man debian/tmp/usr/share/man/man5/mailcap.order.5
# install -m 755 install-mime debian/tmp/usr/sbin/
# install -m 644 install-mime.man debian/tmp/usr/share/man/man8/install-mime.8
install -m 755 update-mime debian/tmp/usr/sbin/
install -m 644 update-mime.man debian/tmp/usr/man/man8/update-mime.8
install -m 644 update-mime.man debian/tmp/usr/share/man/man8/update-mime.8
install -m 755 run-mailcap debian/tmp/usr/bin/
install -m 644 run-mailcap.man debian/tmp/usr/man/man1/run-mailcap.1
install -m 644 rfcs/rfc1521.txt debian/tmp/usr/doc/$(package)/
install -m 644 rfcs/rfc1522.txt debian/tmp/usr/doc/$(package)/
install -m 644 rfcs/rfc1524.txt debian/tmp/usr/doc/$(package)/
install -m 644 debian/changelog debian/tmp/usr/doc/$(package)/changelog.Debian
install -m 644 debian/README debian/tmp/usr/doc/$(package)/copyright
install -m 644 mime-db debian/tmp/var/lib/mime/
install -m 644 run-mailcap.man debian/tmp/usr/share/man/man1/run-mailcap.1
install -m 644 rfcs/* debian/tmp/usr/share/doc/$(package)/
install -m 644 debian/changelog debian/tmp/usr/share/doc/$(package)/changelog.Debian
install -m 644 debian/README debian/tmp/usr/share/doc/$(package)/copyright
install -m 755 debian-view debian/tmp/usr/lib/mime/
install -m 755 playaudio debian/tmp/usr/lib/mime/
install -m 755 playdsp debian/tmp/usr/lib/mime/
install -m 644 mailcap.entries debian/tmp/usr/lib/mime/packages/mime-support
install -m 755 debian/postinst debian/tmp/DEBIAN/postinst
install -m 755 debian/prerm debian/tmp/DEBIAN/prerm
install -m 644 debian/conffiles debian/tmp/DEBIAN/conffiles
cd debian/tmp/usr/man; gzip -9fv */*
cd debian/tmp/usr/doc/$(package); gzip -9v *
cd debian/tmp/usr/doc/$(package); gunzip copyright.gz
cd debian/tmp/usr/share/man; gzip -9fv */*
cd debian/tmp/usr/share/doc/$(package); gzip -9v *
cd debian/tmp/usr/share/doc/$(package); gunzip copyright.gz
cd debian/tmp/usr/bin; ln -s run-mailcap see
cd debian/tmp/usr/bin; ln -s run-mailcap edit
cd debian/tmp/usr/bin; ln -s run-mailcap compose
cd debian/tmp/usr/bin; ln -s run-mailcap print
cd debian/tmp/usr/man/man1; ln -s run-mailcap.1.gz see.1.gz
cd debian/tmp/usr/man/man1; ln -s run-mailcap.1.gz edit.1.gz
cd debian/tmp/usr/man/man1; ln -s run-mailcap.1.gz compose.1.gz
cd debian/tmp/usr/man/man1; ln -s run-mailcap.1.gz print.1.gz
cd debian/tmp/usr/doc/$(package); ln -s rfc1521.txt.gz mime-1.txt.gz
cd debian/tmp/usr/doc/$(package); ln -s rfc1522.txt.gz mime-2.txt.gz
cd debian/tmp/usr/doc/$(package); ln -s rfc1524.txt.gz mailcap.txt.gz
cd debian/tmp/usr/lib/mime/packages; ln -s /var/lib/mime/mime-support-compat mime-support-compat
touch debian/tmp/var/lib/mime/mime-support-compat;
cd debian/tmp/usr/share/man/man1; ln -s run-mailcap.1.gz see.1.gz
cd debian/tmp/usr/share/man/man1; ln -s run-mailcap.1.gz edit.1.gz
cd debian/tmp/usr/share/man/man1; ln -s run-mailcap.1.gz compose.1.gz
cd debian/tmp/usr/share/man/man1; ln -s run-mailcap.1.gz print.1.gz
dpkg-gencontrol -is -ip
chown -R root.root debian/tmp
chmod -R go=rX debian/tmp
......@@ -77,3 +71,8 @@ binary-arch:
binary: binary-indep
@echo "Binaries made"
# local variables:
# tab-width: 8
# end:
......@@ -28,9 +28,9 @@ file.
.B install-mime
is
.B obsolete!
Pluse use
Please use
.B update-mime
insead.
instead.
.SS OPTIONS
All options are in the form --<opt>[=<value>]. Values can be a
......@@ -38,7 +38,7 @@ All options are in the form --<opt>[=<value>]. Values can be a
accepted by dpkg), 'content-type' (any valid content-type as
recognized by MIME), 'conditional' (a valid shell command line), 't/f'
(a true/false or t/f value), 'string', (any arbitrary ascii string),
\'pathname' (a path to an existing file), and 'program-string' (how to
\&'pathname' (a path to an existing file), and 'program-string' (how to
call a program with the given content-type as supported by MIME).
.SS Actions
These options specify what is to be done.
......
application/x-debian-package; /usr/lib/mime/debian-view %s; needsterminal; description=Debian GNU/Linux Package; nametemplate=%s.deb
audio/basic; /usr/lib/mime/playaudio %s; description=Basic uLaw Audio; nametemplate=%s.au
application/x-debian-package; /usr/lib/mime/debian-view %s; needsterminal; description=Debian GNU/Linux Package; nametemplate=%s.deb; priority=0
audio/basic; /usr/lib/mime/playaudio %s; description=Basic uLaw Audio; nametemplate=%s.au; priority=0
.\" Hey, Emacs! This is an -*- nroff -*- source file.
.TH MAILCAP 5 "Release 2" "Bellcore Prototype"
.SH NAME
mailcap - metamail capabilities file
.SH DESCRIPTION
The
.I mailcap
file is read by the
.I metamail
program to determine how to display non-text at the local site.
The syntax of a mailcap file is quite simple, at least compared to termcap files. Any line that starts with "#" is a comment. Blank lines are ignored. Otherwise, each line defines a single mailcap entry for a single content type. Long lines may be continued by ending them with a backslash character, \\.
Each individual mailcap entry consists of a content-type specification, a command to execute, and (possibly) a set of optional "flag" values. For example, a very simple mailcap entry (which is actually a built-in default behavior for metamail) would look like this:
text/plain; cat %s
The optional flags can be used to specify additional information about the mail-handling command. For example:
text/plain; cat %s; copiousoutput
can be used to indicate that the output of the 'cat' command may be voluminous, requiring either a scrolling window, a pager, or some other appropriate coping mechanism.
The "type" field (text/plain, in the above example) is simply any legal content type name, as defined by informational RFC 1524. In practice, this is almost any string. It is the string that will be matched against the "Content-type" header (or the value passed in with -c) to decide if this is the mailcap entry that matches the current message. Additionally, the type field may specify a subtype (e.g. "text/ISO-8859-1") or a wildcard to match all subtypes (e.g. "image/*").
The "command" field is any UNIX command ("cat %s" in the above example), and is used to specify the interpreter for the given type of message. It will be passed to the shell via the system(3) facility. Semicolons and backslashes within the command must be quoted with backslashes. If the command contains "%s", those two characters will be replaced by the name of a file that contains the body of the message. If it contains "%t", those two characters will be replaced by the content-type field, including the subtype, if any. (That is, if the content-type was "image/pbm; opt1=something-else", then "%t" would be replaced by "image/pbm".) If the command field contains "%{" followed by a parameter name and a closing "}", then all those characters will be replaced by the value of the named parameter, if any, from the Content-type header. Thus, in the previous example, "%{opt1}" will be replaced by "something-else". Finally, if the command contains "\\%", those two characters will be replaced by a single % character. (In fact, the backslash can be used to quote any character, including itself.)
If no "%s" appears in the command field, then instead of placing the message body in a temporary file, metamail will pass the body to the command on the standard input. This is helpful in saving /tmp file space, but can be problematic for window-oriented applications under some window systems such as MGR.
Two special codes can appear in the viewing command for objects of type multipart (any subtype). These are "%n" and "%F". %n will be replaced by the number of parts within the multipart object. %F will be replaced by a series of arguments, two for each part, giving first the content-type and then the name of the temporary file where the decoded part has been stored. In addition, for each file created by %F, a second file is created, with the same name followed by "H", which contains the header information for that body part. This will not be needed by most multipart handlers, but it is there if you ever need it.
The "notes=xxx" field is an uninterpreted string that is used to specify the name of the person who installed this entry in the mailcap file. (The "xxx" may be replaced by any text string.)
The "test=xxx" field is a command that is executed to determine whether or not the mailcap line actually applies. That is, if the content-type field matches the content-type on the message, but a "test=" field is present, then the test must succeed before the mailcap line is considered to "match" the message being viewed. The command may be any UNIX command, using the same syntax and the same %-escapes as for the viewing command, as described above. A command is considered to succeed if it exits with a zero exit status, and to fail otherwise.
The "print=xxx" field is a command that is executed to print the data instead of display it interactively. This behavior is usually a consequence of invoking metamail with the "-h" switch.
The "textualnewlines" field can be used in the rather obscure case where metamail's default rules for treating newlines in base64-encoded data are unsatisfactory. By default, metamail will translate CRLF to the local newline character in decoded base64 output if the content-type is "text" (any subtype), but will not do so otherwise. A mailcap entry with a field of "textualnewlines=1" will force such translation for the specified content-type, while "textualnewlines=0" will guarantee that the translation does not take place even for textual content-types.
The "compose" field may be used to specify a program that can be used to compose a new body or body part in the given format. Its intended use is to support mail composing agents that support the composition of multiple types of mail using external composing agents. As with the view-command, the compose command will be executed after replacing certain escape sequences starting with "%". In particular, %s should be replaced by the name of a file to which the composed data is to be written by the specified composing program, thus allowing th3e calling program (e.g. metamail) to tell the called program where to store the composed data. If %s does not appear, then the composed data will be assumed to be written by the composing programs to standard output. The result of the composing program may be data that is NOT yet suitable for mail transport -- that is, a Content-Transfer-Encoding may still need to be applied to the data.
The "composetyped" field is similar to the "compose" field, but is to be used when the composing program needs to specify the Content-type header field to be applied to the composed data. The "compose" field is simpler, and is preferred for use with existing (non-mail-oriented) programs for composing data in a given format. The "composetyped" field is necessary when the Content-type information must include auxilliary parameters, and the composition program must then know enough about mail formats to produce output that includes the mail type information, and to apply any necessary Content-Transfer-Encoding. Conceptually, "compose" specifies a program that simply outputs the specified type of data in its raw form, while "composetyped" specifies a program that outputs the data as a MIME object, with all necessary Content-* headers already in place.
.TP 8
.B needsterminal
If this flag is given, the named interpreter needs to interact with the user on a terminal. In some environments (e.g. a window-oriented mail reader under X11) this will require the creation of a new terminal emulation window, while in most environments it will not. If the mailcap entry specifies "needsterminal" and metamail is not running on a terminal (as determined by isatty(3), the -x option, and the MM_NOTTTY environment variable) then metamail will try to run the command in a new terminal emulation window. Currently, metamail knows how to create new windows under the X11, SunTools, and WM window systems.
.TP 8
.B copiousoutput
This flag should be given whenever the interpreter is capable of producing more than a few lines of output on stdout, and does no interaction with the user. If the mailcap entry specifies copiousoutput, and pagination has been requested via the "-p" command, then the output of the command being executed will be piped through a pagination program ("more" by default, but this can be overridden with the METAMAIL_PAGER environment variable).
.SH BUILT-IN CONTENT-TYPE SUPPORT
The metamail program has built-in support for a few key content-types. In particular, it supports the text type, the multipart and multipart/alternative type, and the message/rfc822 types. This support is incomplete for many subtypes -- for example, it only supports US-ASCII text in general. This kind of built-in support can be OVERRIDDEN by an entry in any mailcap file on the user's search path. Metamail also has rudimentary built-in support for types that are totally unrecognized -- i.e. for which no mailcap entry or built-in handler exists. For such unrecognized types, metamail will write a file with a "clean" copy of the data -- i.e. a copy in which all mail headers have been removed, and in which any 7-bit transport encoding has been decoded.
.SH FILES
$HOME/.mailcap:/etc/mailcap:/usr/share/etc/mailcap:/usr/local/etc/mailcap -- default path for mailcap files.
.SH SEE ALSO
.BR run-mailcap "(1)",
.BR mailcap.order "(5)",
.BR update-mime "(8)"
.SH COPYRIGHT
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.
.SH AUTHOR
Nathaniel S. Borenstein
This diff is collapsed.
###############################################################################
#
# MIME-TYPES and the extensions that represent them
#
# This file is part of the "mime-support" package. Please send email (not a
# bug report) to mime-support@packages.debian.org if you would like new types
# and/or extensions to be added.
#
# Note: Compression schemes like "gzip", "bzip", and "compress" are not
# actually "mime-types". They are "encodings" and hence must _not_ have
# entries in this file to map their extensions. The "mime-type" of an
# encoded file refers to the type of data that has been encoded, not the
# type of the encoding.
#
###############################################################################
application/activemessage
application/andrew-inset
application/applefile
application/atomicmail
application/cu-seeme csm cu
application/dca-rft
application/dec-dx
application/dsptype tsp
application/futuresplash spl
application/ghostview
application/mac-binhex40 hqx
application/macwriteii
application/mathematica nb
application/msaccess mdb
application/msword doc dot
application/news-message-id
application/news-transmission
application/octet-stream bin
application/oda oda
application/pdf pdf
application/pgp-signature pgp
application/postscript ps ai eps
application/remote-printing
application/rtf rtf
application/slate
application/vnd.ms-excel xls xlb
application/vnd.ms-powerpoint ppt pps pot
application/vnd.wap.wmlc wmlc
application/vnd.wap.wmlscriptc wmlsc
application/wita
application/wordperfect5.1 wp5
application/zip zip
application/x-123 wk
application/x-bcpio bcpio
application/x-chess-pgn pgn
application/x-core
application/x-cpio cpio
application/x-csh
application/x-debian-package deb
application/x-director dcr dir dxr
application/x-dms dms
application/x-doom wad
application/x-dvi dvi
application/x-executable
application/x-xfig fig
application/x-font pfa pfb gsf pcf pcf.Z
application/x-gnumeric gnumeric
application/x-gtar gtar tgz taz
application/x-hdf hdf
application/x-httpd-php phtml pht php
application/x-httpd-php3 php3
application/x-httpd-php3-source phps
application/x-httpd-php3-preprocessed php3p
application/x-httpd-php4 php4
application/x-ica ica
application/x-java-applet
application/x-java-archive jar
application/x-java-bean
application/x-java-jnlp-file jnlp
application/x-java-serialized-object ser
application/x-java-vm class
application/x-javascript js
application/x-kdelnk
application/x-kchart chrt
application/x-killustrator kil
application/x-kpresenter kpr kpt
application/x-kspread ksp
application/x-kword kwd kwt
application/x-latex latex
application/x-lha lha
application/x-lzh lzh
application/x-lzx lzx
application/x-maker frm maker frame fm fb book fbdoc
application/x-mif mif
application/x-msdos-program com exe bat dll
application/x-msi msi
application/x-netcdf nc cdf
application/x-ns-proxy-autoconfig pac
application/x-object o
application/x-ogg ogg
application/x-oz-application oza
application/x-perl pl pm
application/x-pkcs7-crl crl
application/x-redhat-package-manager rpm
application/x-rx
application/x-sh
application/x-shar shar
application/x-shellscript
application/x-shockwave-flash swf swfl
application/x-star-office sdd sda
application/x-stuffit sit
application/x-sv4cpio sv4cpio
application/x-sv4crc sv4crc
application/x-tar tar
application/x-tcl
application/x-tex
application/x-tex-gf gf
application/x-tex-pk pk PK
application/x-texinfo texinfo texi
application/x-trash ~ % bak old sik
application/x-troff t tr roff
application/x-troff-man man
application/x-troff-me me
application/x-troff-ms ms
application/x-ustar ustar
application/x-wais-source src
application/x-wingz wz
application/x-x509-ca-cert crt
audio/basic au snd
audio/midi mid midi
audio/mpeg mpga mpega mp2 mp3
audio/mpegurl m3u
audio/prs.sid sid
audio/x-aiff aif aiff aifc
audio/x-gsm gsm
audio/x-pn-realaudio ra rm ram
audio/x-scpls pls
audio/x-wav wav
image/gif gif
image/ief ief
image/jpeg jpeg jpg jpe
image/pcx pcx
image/png png
image/tiff tiff tif
image/vnd.wap.wbmp wbmp
image/x-cmu-raster ras
image/x-coreldraw cdr
image/x-coreldrawpattern pat
image/x-coreldrawtemplate cdt
image/x-corelphotopaint cpt
image/x-djvu djvu djv
image/x-jng jng
image/x-ms-bmp bmp
image/x-portable-anymap pnm
image/x-portable-bitmap pbm
image/x-portable-graymap pgm
image/x-portable-pixmap ppm
image/x-rgb rgb
image/x-xbitmap xbm
image/x-xpixmap xpm
image/x-xwindowdump xwd
inode/chardevice
inode/blockdevice
inode/directory-locked
inode/directory
inode/fifo
inode/socket
message/external-body
message/news
message/partial
message/rfc822
multipart/alternative
multipart/appledouble
multipart/digest
multipart/mixed
multipart/parallel
text/comma-separated-values csv
text/css css
text/english
text/html htm html xhtml
text/mathml mml
text/plain txt text diff
text/richtext rtx
text/tab-separated-values tsv
text/vnd.wap.wml wml
text/vnd.wap.wmlscript wmls
text/xml xml xsl
text/x-c++hdr h++ hpp hxx hh
text/x-c++src c++ cpp cxx cc
text/x-chdr h
text/x-crontab
text/x-csh csh
text/x-csrc c
text/x-java java
text/x-makefile
text/x-moc moc
text/x-pascal p pas
text/x-setext etx
text/x-sh sh
text/x-tcl tcl tk
text/x-tex tex ltx sty cls
text/x-vcalendar vcs
text/x-vcard vcf
video/dl dl
video/fli fli
video/gl gl
video/mpeg mpeg mpg mpe
video/quicktime qt mov
video/x-mng mng
video/x-ms-asf asf asx
video/x-msvideo avi
video/x-sgi-movie movie
x-world/x-vrml vrm vrml wrl
This diff is collapsed.
This diff is collapsed.
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<TITLE>rfc1524 - A User Agent Configuration Mechanism For Multimedia M</TITLE>
<LINK REV="made" HREF="mailto:rfc-admin@faqs.org">
<META name="description" content="A User Agent Configuration Mechanism For Multimedia Mail Format Information">
<META name="authors" content="N. Borenstein">
<META name="date" content="September 1993">
<META name="status" content="INFORMATIONAL">
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000">
<P ALIGN=CENTER><STRONG><FONT SIZE="-1">Internet RFC/STD/FYI/BCP Archives</FONT></STRONG></P>
<P ALIGN=CENTER><IMG SRC="/images/library.jpg" HEIGHT=62 WIDTH=150 BORDER="0" ALIGN="MIDDLE" ALT=""></P>
<H1 ALIGN=CENTER>RFC1524</H1>
<DIV ALIGN=CENTER>[ <A HREF="/rfcs/index.html">Index</A> |
<A HREF="/rfcs/rfcsearch.html">Search</A> |
<A HREF="/rfcs/changed.html">What's New</A> |
<A HREF="mailto:rfc-admin@faqs.org">Comments</A> |
<A HREF="/rfcs/rfchelp.html">Help</A> ]
</DIV>
<HR SIZE=2 NOSHADE>
<PRE>
Network Working Group N. Borenstein
Request for Comments: 1524 Bellcore
Category: Informational September 1993
A User Agent Configuration Mechanism
For Multimedia Mail Format Information
......@@ -33,8 +55,8 @@ Introduction
The electronic mail world is in the midst of a transition from
single-part text-only mail to multi-part, multi-media mail. In
support of this transition, various extensions to RFC 821 and RFC 822
have been proposed and/or adopted, notably including MIME [RFC-1521].
support of this transition, various extensions to <A HREF="http://www.faqs.org/rfcs/rfc821.html">RFC 821</A> and <A HREF="http://www.faqs.org/rfcs/rfc822.html">RFC 822</A>
have been proposed and/or adopted, notably including MIME [<A HREF="http://www.faqs.org/rfcs/rfc1521.html">RFC-1521</A>].
Various parties have demonstrated extremely high-functionality
multimedia mail, but the problem of mail interchange between
different user agents has been severe. In general, only text
......@@ -47,13 +69,6 @@ Introduction
unfamiliar (non-text) type, they consult an external file for
information on how to display that file. That file might say, for
Borenstein [Page 1]
RFC 1524 Multimedia Mail Configuration September 1993
example, that if the content-type of a message is "foo" it can be
displayed to the user via the "displayfoo" program.
......@@ -101,17 +116,8 @@ Overall Format of a Mailcap File
entry. Note that for such "continued" lines, the backslash must be
the last character on the line to be continued.
Borenstein [Page 2]
RFC 1524 Multimedia Mail Configuration September 1993
Thus the overall format of a mailcap file is given, in the modified
BNF of RFC 822, as:
BNF of <A HREF="http://www.faqs.org/rfcs/rfc822.html">RFC 822</A>, as:
Mailcap-File = *Mailcap-Line
......@@ -119,7 +125,7 @@ RFC 1524 Multimedia Mail Configuration September 1993
Comment = NEWLINE / "#" *CHAR NEWLINE
NEWLINE = <newline as defined by OS convention>
NEWLINE = &lt;newline as defined by OS convention&gt;
Note that the above specification implies that comments must appear
on lines all to themselves, with a "#" character as the first
......@@ -159,13 +165,6 @@ Format of a Mailcap Entry
-- The "composetyped" field is similar to the "compose" field, but is
to be used when the composing program needs to specify the
Borenstein [Page 3]
RFC 1524 Multimedia Mail Configuration September 1993
Content-type header field to be applied to the composed data. The
"compose" field is simpler, and is preferred for use with existing
(non-mail-oriented) programs for composing data in a given format.
......@@ -214,14 +213,6 @@ RFC 1524 Multimedia Mail Configuration September 1993
that it is probably a mistake if needsterminal and copiousoutput
are both specified.
Borenstein [Page 4]
RFC 1524 Multimedia Mail Configuration September 1993
-- The "description" field simply provides a textual description,
optionally quoted, that describes the type of data, to be used
optionally by mail readers that wish to describe the data before
......@@ -264,20 +255,9 @@ RFC 1524 Multimedia Mail Configuration September 1993
application/postscript; ps-to-terminal %s;\ needsterminal
application/postscript; ps-to-terminal %s; \compose=idraw %s
In RFC 822 modified BNF, the following grammar describes a mailcap
In <A HREF="http://www.faqs.org/rfcs/rfc822.html">RFC 822</A> modified BNF, the following grammar describes a mailcap
entry:
Borenstein [Page 5]
RFC 1524 Multimedia Mail Configuration September 1993
Mailcap-Entry = typefield ; view-command
[";" 1#field]
......@@ -295,7 +275,7 @@ RFC 1524 Multimedia Mail Configuration September 1993
mchar = schar / qchar
schar = * <any CHAR except ";","\", and CTLS>
schar = * &lt;any CHAR except ";","\", and CTLS&gt;
qchar = "\" CHAR ; may quote any char
......@@ -323,17 +303,6 @@ RFC 1524 Multimedia Mail Configuration September 1993