Upstream software project

kmail

Mail client

About kmail

Mail client

This project links 4 native package records across 2 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.

Project pictures and package coverage

Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.kmail: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
kmail
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
fedora-43, fedora-44
License expression
BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND LGPL-2.0-only AND LGPL-2.0-or-later AND (GPL-2.0-only OR GPL-3.0-only)
Source repository
Not reported

Source-reported description

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

Runtime libraries for kmail.

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.

Fedora 43

  1. Package kmail

    43 (Fedora 43) (Unspecified): Mail client

    26.04.3-1.fc43: aarch64 x86_64

    Source: kmail

  2. Package kmail-libs

    43 (Fedora 43) (Unspecified): Runtime libraries for kmail

    26.04.3-1.fc43: aarch64 x86_64

    Source: kmail

Fedora 44

  1. Package kmail

    44 (Fedora 44) (Unspecified): Mail client

    26.08.0-1.fc44: aarch64 x86_64

    Source: kmail

  2. Package kmail-libs

    44 (Fedora 44) (Unspecified): Runtime libraries for kmail

    26.08.0-1.fc44: aarch64 x86_64

    Source: kmail

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.