Linux workstation

Upstream software project

mailcap

Helper application and MIME type associations for file types (documentation)

About mailcap

Helper application and MIME type associations for file types (documentation)

This project links 10 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Alpine Linux 3.21: 2 package records; Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.mailcap: recorded package coverageAlpine Linux 3.212 recordsAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
mailcap
Publisher
Not authoritatively mapped
Native package records
10
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, fedora-43, fedora-44
License expression
Public Domain
Metadata completeness
55/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The mailcap file is used by the metamail program. Metamail reads the mailcap file to determine how it should display non-text or multimedia material. Basically, mailcap associates a particular type of file with a particular program that a mail agent or other program can call in order to handle the file. Mailcap should be installed to allow certain programs to be able to handle non-text files. Also included in this package is the mime.types file which contains a list of MIME types and their filename "extension" associations, used by several applications e.g. to determine MIME types for filenames.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Alpine Linux 3.21

  1. mailcap

    Alpine Linux 3.21 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types

    aarch64x86_64v3.21
  2. mailcap-doc

    Alpine Linux 3.21 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types (documentation)

    aarch64x86_64v3.21

Alpine Linux 3.22

  1. mailcap

    Alpine Linux 3.22 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types

    aarch64x86_64v3.22
  2. mailcap-doc

    Alpine Linux 3.22 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types (documentation)

    aarch64x86_64v3.22

Alpine Linux 3.23

  1. mailcap

    Alpine Linux 3.23 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types

    aarch64x86_64v3.23
  2. mailcap-doc

    Alpine Linux 3.23 / source mailcap

    2.1.54-r0

    Helper application and MIME type associations for file types (documentation)

    aarch64x86_64v3.23

Fedora 43

  1. mailcap

    Fedora 43 / Unspecified / source mailcap

    2.1.54-9.fc43

    Helper application and MIME type associations for file types

    noarch43
  2. nginx-mimetypes

    Fedora 43 / Unspecified / source mailcap

    2.1.54-9.fc43

    MIME type mappings for nginx

    noarch43

Fedora 44

  1. mailcap

    Fedora 44 / Unspecified / source mailcap

    2.1.54-10.fc44

    Helper application and MIME type associations for file types

    noarch44
  2. nginx-mimetypes

    Fedora 44 / Unspecified / source mailcap

    2.1.54-10.fc44

    MIME type mappings for nginx

    noarch44

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.