Tnef

Aus Foxwiki

tnef - decode Microsoft's Transport Neutral Encapsulation Format

Beschreibung

TNEF ist ein Programm zur Dekomprimierung von MIME-Anhängen des Typs »application/ms-tnef«

  • Dies ist ein typischer Microsoft-Anhang

Das Programm ermöglicht das Auspacken von in TNEF eingekapselten Anhängen

  • Dies mildert die Notwendigkeit des Gebrauches von Microsoft Outlook, um diese Anhänge zu betrachten

This manual page documents the tnef filter

  • tnef decodes e-mail attachments encoded in Microsoft's Transport Neutral Encapsulation Format (hereafter, TNEF), which "wraps" Microsoft e-mail attachments

Unfortunately, these "wrapped" attachments are inaccessible to any e-mail client that does not understand TNEF

  • Fortunately, the tnef filter can be used by any MIME-aware client to unpack these attachments

Installation

# apt install tnef

Syntax

$ tnef [options] [FILE]
$ tnef {--help | --version}

Optionen

Option Beschreibung
f FILE, --file=FILE use FILE as input ('-' denotes stdin).
  • When this option is omitted, tnef reads data from stdin.
C DIR, --directory=DIR unpack file attachments into DIR.
x SIZE, --maxsize=SIZE limit maximum size of extracted archive (bytes)
t, --list list attached files, do not extract.
  • For each file in the datafile the file name and full path will be printed.

If the verbose option is also provided then this option acts as the --list-with-mime-types option and also prints the file length (in bytes) and the date of the file before the other data.

-list-with-mime-types same as list option but also prints MIME type and content ID of each file after filename and file path.
w, --interactive, --confirmation ask for confirmation for every action.
-overwrite when extracting attachments, overwrite existing files.
-number-backups when extracting attachments, if file FOO will be overwritten, create FOO.n instead.
-use-paths honor file pathnames specified in the TNEF attachment.
  • For security reasons, paths to attached files are ignored by default.
-save-body FILE Save message body data found in the TNEF data.
  • By default tnef only extracts the attached files and not the message body.

There can be up to three message bodies in the file, plain text, HTML encoded, and RTF encoded.

  • Which are saved is specified by the --body-pref option.
  • By default the message bodies are written to a file named message with an extension based upon the type (txt, html, rtf).
-body-pref PREF Specifies which of the possibly three message body formats will be saved.
  • PREF can be up to three characters long and each character must be

one of 'r', 'h', or 't' specifying RTF, HTML or text.

  • The order is the order that the data will be checked, the first type found will be

saved.

  • If PREF is the special value of 'all' then any and all message body data found will be saved.
  • The default is 'rht'.
-save-rtf FILE DEPRECATED.
  • Equivalent to --save-body=FILE --body-pref=r
h, --help show usage message
V, --version display version and copyright
v, --verbose produce verbose output
-debug enable debug output. (This will produce a very large amount of output.)

Parameter

Umgebungsvariablen

Exit-Status

Anwendungen

Fehlerbehebung

Konfiguration

Dateien

Siehe auch

  1. metamail(1)
  2. mailcap(4)
  3. mutt(1)
  4. other email clients

Sicherheit

Dokumentation

RFC

Man-Pages

Info-Pages

Links

Einzelnachweise


Projekt

Weblinks

  1. https://www.dwheeler.com/essays/microsoft-outlook-tnef.html


Testfragen

Testfrage 1

Antwort1

Testfrage 2

Antwort2

Testfrage 3

Antwort3

Testfrage 4

Antwort4

Testfrage 5

Antwort5

libkf5tnef5

Bibliothek zur Handhabung von TNEF-Daten

Die Bibliothek Ktnef kann Daten im TNEF-Format handhaben. (Transport Neutral Encapsulation Format ist ein proprietäres Format von E-Mail-Anhängen, das von Microsoft Outlook und Microsoft Exchange Server verwendet wird.) Die API ermöglicht einen Zugriff auf die Anhänge und die Nachrichteneigenschaften (TNEF/MAPI). Außerdem kann man mit Ktnef im Rich Text Format verfasste Nachrichten ansehen/extrahieren.

Manpage

KNOWN LIMITATIONS

tnef ignores the OEMCodePage data in the data file. It assumes Unicode data.