CVE and update status of the FreeBSD ports tree3,864 unaddressed CVEs in 671 portsAll times are CET
Port details

mail/mmh 0.4_1

CLI mail user agent, fork from nmh

Port info

Maintainer
satanist+freebsd@bureaucracy.de
Packages
latest: 0.4_1
Upstream
up to date
Last update
to 0.4_1 · 2453ff3a9d
Quarterly
2026Q4: 0.4_1
WWW
http://marmaro.de/prog/mmh/
Links
cgit · VuXML

Install

Package
# pkg install mmh
installs 0.4_1 from latest; from quarterly (2026Q4) 0.4_1
Port
# cd /usr/ports/mail/mmh && make install clean
# make -C /usr/ports/mail/mmh config  # change options first
Size
534 KiB download · 2.5 MiB installed
Depends on
nothing
License
BSD3CLAUSE
Options
1 of 4 on in the package: FLOCK
Show the 3 options that are off
DOT FCNTL LOCKF

Packages by version and architecture

latest

FreeBSD versionamd64aarch64i386
FreeBSD 160.4_10.4_1–
FreeBSD 150.4_10.4_1–
FreeBSD 140.4_10.4_10.4_1

quarterly (2026Q4)

FreeBSD versionamd64aarch64i386
FreeBSD 150.4_10.4_1–
FreeBSD 140.4_10.4_10.4_1

version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.

Unaddressed and VuXML only (0)

No unaddressed CVE and nothing reported by pkg audit for the packaged version 0.4_1.

Fixed (0)

No VuXML entries for this package.

Problem reports (1) · open in Bugzilla, most recently changed first

PRSummaryStatusChanged
299187maintainer-feedback? mail/mmh: fix typos in MakefileNew2026-10-07

Commits (10)

Muhammad Moinur Rahman (bofh) · 0.4_1
mail/mmh: Moved man to share/man

Approved by:    portmgr (blanket)
2453ff3a9d
Stefan Eßer (se) · 0.4
Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)
fb16dfecae
Stefan Eßer (se) · 0.4
Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)
b7f05445c0
Stefan Eßer (se) · 0.4
Fix CONFLICTS entries of multiple ports

There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.

This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.

Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
cannot conflict with itself (due to logic in bsd.port.mk that
supresses the pattern match result in that case).

A few ports that set the conflicts variables depending on complex
conditions (e.g. port options), have been left unmodified, despite
probably containing outdated package names.

These changes should only affect the installation of locally built
ports, not the package building with poudriere. They should give an
early indication of the install conflict in cases where currently
the pkg command aborts an installation when it detects that an
existing file would be overwritten,

Approved by:	portmgr (implicit)
bcaf25a8c8
Stefan Eßer (se) · 0.4
*/*: Remove redundant '-*' from CONFLICTS definitions

The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").

Approved by: portmgr (blanket)
04b9da4140
Stefan Eßer (se) · 0.4
*/*: Remove redundant '-[0-9]*' from CONFLICTS

The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").

Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".

Approved by:	portmgr (blanket)
819f25b36d
Mathieu Arnold (mat) · 0.4
One more small cleanup, forgotten yesterday. Reported by:	lwhsu
cf118ccf87
Mathieu Arnold (mat) · 0.4
Remove # $FreeBSD$ from Makefiles.
305f148f48
Kyle Evans (kevans) · 0.4
mail/mmh: fix build with -fno-common

mmh had just a minor build issue with -fno-common, fixed with a trivial
patch to extern the variable in question.

PR:		248812
Approved by:	satanist+freebsd@bureaucracy.de (maintainer)
MFH:		2020Q3 (build fix: -fno-common)
8788f96ef4
Kurt Jaeger (pi) · 0.4
New port: mail/mmh

Mmh is a modified version of the electronic mail handling system nmh.
Nmh (new MH) itself was originally based on the package MH-6.8.3, and
was intended to be a (mostly) compatible drop-in replacement for MH.
In contrast, mmh is not intended to be a drop-in replacement for nmh,
but rather aims for the modernization and simplification of nmh,
accepting reduced compatiblity if it, at the same time, allows to
achieve greater goals from mmh's point of view.

WWW: http://marmaro.de/prog/mmh/

PR:		245346
Submitted by:	satanist+freebsd@bureaucracy.de
08db3b55d2