BSD Ports

mail/bogofilter MidnightBSD

System
MidnightBSD
Repository
mports
Last update
Commit
b2dfe62186
Categories

Description

In the other systems

The newest version among them is 1.3.0.r1, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
MidnightBSDmail/bogofilterno data--2026-08-09
FreeBSDmail/bogofilter1.3.0.r1_5 newestnone knownDeprecated[email protected]2026-10-20
OpenBSDmail/bogofilter1.2.5no data-Marc Espie <[email protected]>2026-09-24
NetBSDmail/bogofilter1.2.4nb34none known-[email protected]-
GhostBSDmail/bogofilter1.3.0.r1_4 newestno data-[email protected]-

Compare across BSDs

Install

Binary package:

mport install bogofilter

From mports:

cd /usr/mports/mail/bogofilter && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	bogofilter>0:mail/bogofilter

Dependencies

As this port's Makefile names them.

Library 1

No port depends on this one.

Related ports

The same software or family in MidnightBSD: one homepage, or one name but for a version or a variant.

Commit history 1

DateCommitCreditsLog message
b2dfe62186 Lucas Holt mail/bogofilter-bdb: update to 1.3.0.rc1 (#732)
Update `mail/bogofilter-bdb` (master) and its `mail/bogofilter` slave from 1.2.5 to 1.3.0.rc1, matching FreeBSD. ## The real bug this bump exposed **bogofilter 1.3.0 changed configure's default backend from `db` to `sqlite3`** (`WITH_DB_ENGINE=sqlite3` at `configure:9554`). The mports master never passed `--with-database` — it relied on the 1.2.5 default. The first master build therefore produced a **SQLite** binary that still linked `libdb-5.3` via `BF_LIBS` and **passed its entire test suite**. Only `bogofilter -V` reporting `bogofilter-sqlite … Database: SQLite 3.50.4` caught it. Fixed with an explicit `--with-database=db` inside the master's `.if MASTERDIR == .CURDIR` guard; it now reports `Database: Berkeley DB 5.3.28`. …