Postfix 3.11.1 resolves several lingering issues that had been causing headaches after previous upgrades. The patch corrects an alias_map error triggered by a missing default_database_type in main.cf, which administrators often overlook during migrations; adding the line back stops mail delivery stalls at lookup time. A buffer over‑read bug from 3.0 that crashed Postfix when an enhanced status code like “5.7.2” appeared without follow‑up text has been fixed, preventing errant crashes in heavy traffic scenarios. Finally, nbdb_reindexd(8) now propagates service_name properly and suppresses unnecessary error messages when automatic re‑indexing is disabled, keeping logs cleaner for operators.

Postfix 3.11.1 Release Fixes Alias Map Errors and Buffer Over‑Read Bugs

The newest Postfix version, 3.11.1, arrives with a handful of targeted fixes that should make life a little easier for anyone who’s ever wrestled with alias resolution or mysterious status code errors.

Postfix 3.11.1 Bug Fixes

A long‑standing glitch that crept in during the 3.0 release is finally squashed. The patch stops an alias_map error that shows up when the default_database_type setting is missing from main.cf. Administrators who upgraded from older releases often forget to re‑add this line, and when they did, mail delivery would stall at the alias lookup stage. Fixing it simply involves adding or uncommenting the appropriate default_database_type entry in the configuration file—no extra tools required.

Another subtle issue that slipped in with Postfix 3.3 has been corrected: a null pointer crash in nbdb_reindexd(8) caused by a missing service_name value. The patch ensures the value is propagated automatically, so systems that rely on nbdb re‑indexing won’t see sudden service restarts or error logs.

There’s also a defensive tweak to the startup sequence of nbdb_reindexd(8). When the non_bdb_migration_level flag disables automatic re‑indexing, Postfix now suppresses a spurious error message that previously banged against the console. The change keeps log files cleaner and reduces noise for operators.

Buffer Over‑Read Fix: A Rare but Painful Case

A bug introduced in 3.0 caused a buffer over‑read when Postfix processed an enhanced status code without any accompanying text. In practice, this manifested as a crash or corrupted log entry whenever a configuration file contained something like “5.7.2” by itself—no explanatory string following the three‑digit code. The fix removes the over‑read and validates that a proper message accompanies such codes.

While this pattern is uncommon, it shows how Postfix’s flexibility can backfire if you stray from the typical syntax. Administrators who have customized access tables or header checks with bare status codes should double‑check those entries after upgrading to 3.11.1.

Getting the Update

The source code and binary packages for 3.11.1 are available at the official mirrors. Depending on your distribution, you can either compile from source or install via your package manager if a new repo is already in place. The upgrade path is straightforward: stop Postfix, replace the binaries, run postconf -n to confirm settings are intact, and start the service again.

Many users have reported that applying these fixes resolved delivery loops caused by alias_map errors—especially on servers with custom database backends where default_database_type had been inadvertently omitted. The buffer over‑read patch has also prevented a handful of unexpected crashes noted in log files during heavy SMTP traffic periods.

That’s the short version: Postfix 3.11.1 cleans up a few nasty bugs, improves stability for alias resolution and status code handling, and keeps the logs quiet when re‑indexing is disabled. If your mail server has been behaving oddly after an upgrade or if you run custom status codes, give this release a spin.