Thanks for your input. I really wanted to avoid multiple instances so I finally
configured it by re-writing domain.com rcpts to a local mailbox
domain.com.backup on the public interface:
mynetworks = 127.0.0.0/8
mailbox_size_limit = 0
inet_protocols = ipv4
myhostname = domain.com
mydestination =
biff = no
append_dot_mydomain = no
soft_bounce = yes
relayhost = ***************
smtp_sasl_password_maps = ***************
smtp_use_tls=yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_tls_CAfile=/etc/ssl/certs/ca-certificates.crt
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated
defer_unauth_destination
compatibility_level=2
#
#
$accept_domain_com=check_recipient_access inline:{{domain.com=REDIRECT
m...@domain.com.backup}} check_recipient_access inline:{domain.com=OK} reject
virtual_mailbox_domains = domain.com.backup
virtual_mailbox_base = /home/archive
virtual_mailbox_maps = static:mail/
virtual_uid_maps = static:1000
virtual_gid_maps = static:1000
master.cf:
xx.xx.x.x:smtp inet n - y - - smtpd -o
smtpd_relay_restrictions=$accept_domain_com
127.0.0.1:smtp inet n - y - - smtpd
----- Original message -----
From: Wietse Venema <wie...@porcupine.org>
To: Postfix users <postfix-users@postfix.org>
Subject: Re: How to act based on the interface on which the mail was received?
Date: Mon, 11 Feb 2019 19:20:38 -0500 (EST)
RA:
> Thanks for your response. Would want to avoid running multiple
> instances as far as possible. I feel I am missing something in the
> configuration or my approach isn't correct. Postfix should be able
> to handle this trivial task in a single instance.
It's not trivial. Postfix routing can depend on destination
or (to some extent) on source, but it cannot depend on both.
Wietse
