LINUXOR.SK ... open source notes ...

Email - Postfix transport table, internal servers

category: solutionz · date: 2019-12-31 · updated: 2026-10-02 · author: LALA

Email Solution · Config document · referenced from Internal servers: Postfix

The transport table of the internal pair. It has one entry: mail for the site's own domain goes by SMTP to the third internal server, which holds the mailboxes. Everything not listed here follows relayhost in main.cf and leaves through the relay servers.

ItemValue
Path on the server/etc/postfix/transport
Shown hereDC2-A-VCMSX001
Also onDC2-B-VCMSX001, identical; DC2-A-VCMSX002 with another transport (below)
Referenced bytransport_maps = hash:/etc/postfix/transport in main.cf
Activated withpostmap /etc/postfix/transport, which a hash: table needs; the install notes show only the edit with vi

The file

ini
###################################################################################################
# Domain/mail_address   Transport
###################################################################################################
# Delivery transport to Internal Email Server for email messages for domain @ad-dc2.example.net
ad-dc2.example.net          smtp:[10.12.19.43]

Differences on the other hosts

HostLineValue
DC2-B-VCMSX001whole filethe same, plus one empty line at the end
DC2-A-VCMSX002ad-dc2.example.netdovecot, the pipe service of master.cf that hands the message to the Dovecot delivery agent

The square brackets around 10.12.19.43 switch off the MX lookup for the next hop. The first concept of 2018 had one internal server per site, and its table read ad.example.net dovecot: the server that accepted the message also delivered it. Splitting acceptance and mailboxes over two kinds of server turned that line into an SMTP hop on the pair and left the original line on the mailbox server.

Checked against Postfix 3.11

As builtToday
hash: table, built with postmap into a Berkeley DB fileRHEL 10 no longer provides the Berkeley DB libraries; the default table type of its Postfix is lmdb: and existing tables have to be converted. Postfix 3.11 describes the migration in NON_BERKELEYDB_README
next hop smtp:[10.12.19.43]unchanged syntax
relayhost and smtp_fallback_relay for everything elseboth still valid under these names

The content needs no change; the table type does.

← solutionz