summaryrefslogtreecommitdiff
path: root/mail/tnef2txt/DESCR
diff options
context:
space:
mode:
authordrochner <drochner>2002-02-14 13:16:36 +0000
committerdrochner <drochner>2002-02-14 13:16:36 +0000
commit003fff6ecf46a749517803fbf05edd2fa3507aeb (patch)
tree792df9a64a7907d51d40fc882a29deb888979ee7 /mail/tnef2txt/DESCR
parent9720e77aebbb842aee145f01e4a6e08e14dcaa9e (diff)
downloadpkgsrc-003fff6ecf46a749517803fbf05edd2fa3507aeb.tar.gz
import of tnef2txt-1.4, a portable application/ms-tnef parser
Diffstat (limited to 'mail/tnef2txt/DESCR')
-rw-r--r--mail/tnef2txt/DESCR19
1 files changed, 19 insertions, 0 deletions
diff --git a/mail/tnef2txt/DESCR b/mail/tnef2txt/DESCR
new file mode 100644
index 00000000000..c4c79c9d1b8
--- /dev/null
+++ b/mail/tnef2txt/DESCR
@@ -0,0 +1,19 @@
+Several Microsoft Windows email applications support the Transport Neutral
+Encapsulation Format (TNEF). This is a method for MAPI compliant mail programs
+to transfer data to each other across gateways. Generally, a mail agent will
+create a MIME multipart message containing the text body of the mail message,
+and a single attachment of type application/ms-tnef. This attachment at least
+follows the format of MIME messages, if not the intent. Usually, this bitstream
+contains no more information than is already contained in the headers and body
+of the message, but instead of attaching attachments to the email message as
+separate MIME attachments, they are included in the TNEF attachment. To handle
+this, I wrote a program tnef2txt which will dump the information in the TNEF
+bitstream, and also dump files to disk which are contained in the bitstream.
+Just run the program without arguments for usage information. You can call this
+program from a mailcap file with the following line:
+
+application/ms-tnef; tnef2txt %s; copiousoutput
+
+or, if you wish to save attachments to disk which are in the bitstream:
+
+application/ms-tnef; tnef2txt -s %s; copiousoutput