Install tnef with Homebrew, apk, apt, dnf, MacPorts, Nix, zypper

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• tnef

Project history

The project history is unusually well preserved in its NEWS file. It began with a 0.6 first public release, reached 1.0 with MAPI attribute parsing and long filename support, and then accumulated the practical fixes expected of a mail-attachment unpacker: safer path handling, tar-like command options, automated tests, NetBSD and big-endian portability, Mac OS X configuration fixes, MIME type listing, RTF body saving, Unicode handling, and memory/security hardening.

Development reflects the long tail of interoperability with proprietary mail formats. The README explains the reason for the tool: Outlook and Exchange caused more mail to be wrapped in Microsoft's TNEF format, and this program let users extract attachments without needing Microsoft Outlook. Later NEWS entries show maintenance around Unicode filenames, multi-value MAPI attributes, allocator hardening, integer overflow checks, null pointer avoidance, and malicious input handling.

Adoption history

TNEF became a classic packaging target because it solves a small but recurring system-administration problem. The supplied package facts list Homebrew, Debian, Ubuntu, Alpine, Fedora/DNF, MacPorts, Nix, and openSUSE/Zypper packaging, showing that it is carried broadly despite its narrow scope.

The README says it is mainly tested and used on GNU/Linux and Cygwin and should work on other Unix-like systems. That portability claim matches its package footprint: it is the kind of single-purpose C utility that distributions keep available so mail clients, scripts, and users can recover attachments from Microsoft-heavy environments.

How it is used

Users run `tnef` against a TNEF attachment to list or extract embedded files, message bodies, MIME types, or RTF data depending on options. Its normal role is not a daemon or workflow manager but a rescue utility for mail attachments that arrived in a Microsoft-only wrapper.

The project is especially useful in mixed Unix/Windows organizations, where a developer, sysadmin, or mail user may receive an attachment that is unreadable in a standard Unix mail client.

Why package nerds care

For package nerds, TNEF is a good example of a tiny utility that earns wide distribution packaging because it removes friction at an old interoperability boundary. It is not glamorous, but it turns a proprietary mail wrapper into ordinary files using normal Unix command-line patterns.

Its NEWS file is also a reminder that small parsers for hostile or malformed file formats need maintenance: many later releases are about bounds checks, overflows, Unicode edge cases, and safer extraction behavior.

Timeline

• 0.6: First public release.
• 1.0: Added MAPI attribute parsing and long filename support.
• 2003: 1.2.2 added `--maxsize` for protection against hostile TNEF files.
• 2006: 1.3.3 added message body saving and Unicode handling.
• 2011: 1.4.8 switched to Git.
• 2017: 1.4.13 fixed security issues reported by external researchers.
• 2019: 1.4.18 improved strdup safety and corrected a bit-shift issue.

Related projects

• Related to Unix mail clients and scripts that need to recover files from Outlook/Exchange `winmail.dat` attachments.
• Adjacent to other TNEF/MAPI parsers, but this package is the long-standing command-line unpacker distributed by Unix package managers.

Sources

• https://github.com/verdammelt/tnef#readme
• https://github.com/verdammelt/tnef/blob/master/ChangeLog
• https://github.com/verdammelt/tnef/blob/master/NEWS
• input source_facts.package-manager