docker-mailserver/docs/content/examples/use-cases/bind-smtp-network-interface.md

title	hide
Use Cases | Binding outbound SMTP to a specific network	toc

!!! warning "Advice not extensively tested"

This configuration advice is a community contribution which has only been verified as a solution when using `network: host`, where you have direct access to the host interfaces.

It may be applicable in other network modes if the container has control of the outbound IPs to bind to. This is not the case with bridge networks that typically bind to a private range network for containers which are bridged to a public interface via Docker.

If your Docker host is running multiple IPv4 and IPv6 IP-addresses, it may be beneficial to bind outgoing SMTP connections to specific IP-address / interface.

• When a mail is sent outbound from DMS, it greets the MTA it is connecting to with a EHLO (DMS FQDN) which might be verified against the IP resolved, and that a PTR record for that IP resolves an address back to the same IP.
• A similar check with SPF can be against the envelope-sender address which may verify a DNS record like MX / A is valid (or a similar restriction check from an MTA like Postfix has with reject_unknown_sender).
• If the IP address is inconsistent for those connections from DMS, these DNS checks are likely to fail.

This can be configured by overriding the default Postfix configurations DMS provides. Create postfix-master.cf and postfix-main.cf files for your config volume (docker-data/dms/config).

In postfix-main.cf you'll have to set the smtp_bind_address and smtp_bind_address6 to the respective IP-address on the server you want to use.

!!! example

=== "Contributed solution"

    ```title="postfix-main.cf"
    smtp_bind_address = 198.51.100.42
    smtp_bind_address6 = 2001:DB8::42
    ```

    !!! bug "Inheriting the bind from `main.cf` can misconfigure services"

        One problem when setting `smtp_bind_address` in `main.cf` is that it will be inherited by any services in `master.cf` that extend the `smtp` transport. One of these is `smtp-amavis`, which is explicitly configured to listen / connect via loopback (localhost / `127.0.0.1`).

        A `postfix-master.cf` override can workaround that issue by ensuring `smtp-amavis` binds to the expected internal IP:

        ```title="postfix-master.cf"
        smtp-amavis/unix/smtp_bind_address=127.0.0.1
        smtp-amavis/unix/smtp_bind_address6=::1
        ```

=== "Alternative (unverified)"

    A potentially better solution might be to instead [explicitly set the `smtp_bind_address` override on the `smtp` transport service][gh-pr::3465::alternative-solution]:

    ```title="postfix-master.cf"
    smtp/inet/smtp_bind_address = 198.51.100.42
    smtp/inet/smtp_bind_address6 = 2001:DB8::42
    ```

    If that avoids the concern with `smtp-amavis`, you may still need to additionally override for the [`relay` transport][gh-src::postfix-master-cf::relay-transport] as well if you have configured DMS to relay mail.

!!! note "IP addresses for documentation"

IP addresses shown in above examples are placeholders, they are IP addresses reserved for documentation by IANA (_[RFC-5737 (IPv4)][rfc-5737] and [RFC-3849 (IPv6)][rfc-3849]_). Replace them with the IP addresses you want DMS to send mail through.