Many default Postfix installations (especially on Debian/Ubuntu) run daemons inside a "chroot" jail for security. If a system update upgrades a core library (like libc or libresolv ) but the files inside the chroot jail are not updated, the transport agent will crash instantly.
Postfix uses hash database files (e.g., transport.db , aliases.db , virtual.db ) for efficient lookups. If these .db files are outdated, corrupted, or mismatched with their source text files, Postfix may be unable to find the correct routing information. The error message warning: transport_maps lookup failure is a strong indicator of this problem. After making changes to any text file used by a hash: map, you must run the postmap command to regenerate the associated .db file.
Run this command to search your logs for the suspension and view the surrounding context:
This error triggers when Postfix is instructed to use a transport name that it does not recognize, cannot find in its master configuration, or cannot execute due to system-level restrictions. Step 1: Analyze Your Mail Logs
This error often appears in logs as: status=deferred (delivery temporarily suspended: unknown mail transport error (upd)) Or sometimes with a variation indicating an issue with configuration.
postfix check
If the error persists after a configuration change, you may need to the affected messages rather than just flushing them.
A large number of "unknown mail transport error" instances are rooted in the server's inability to look up the required DNS records. Postfix needs to resolve either the MX record for the recipient's domain or an A record for a specified relayhost. If nsswitch.conf or the local DNS resolver is misconfigured, or if the upstream DNS server is unreachable, the lookup will fail. The error message might then show: Name service error for name=example.com type=MX: Host not found, try again . This is often a transient network issue but can also be a permanent DNS configuration error.
Run this command to view recent activity: