From: Joerg Friedrich (Joerg.Dieter.Friedrichuni-konstanz.de)
Date: Fri Apr 02 2004 - 01:44:35 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

We have the following setup:
2 Servers (bastions) running postfix which only handle mailtransport
from/to the internet, and 2 servers (maildispatcher) handling all mails
with intranet servers.

In DNS the bastions are listed as Mailexchanger for our domain uni-konstanz.de
as well as some other domains.

ATM all these domains are listed in main.cf as relay_domains.
Additionally we have defined a transport for each domain to the 2
maildispatchers.

Problem: Someone at the university registers a domain and whishes to
route the mail through our system. (Mostly "I'm Professor xy, I need this
now, there is important ....")
the domain has to be 'registered' at two places (relay_domains in
main.cf and transport table)

My idea:
1. defining relay_domains = dbm:/etc/postfix/relay_domains in main.cf,
2. pointing relay_transport to the maildispatchers (we have an additional
   'MX-domain' for the dispatchers)
   relay_transport=relay:dispatchers.uni-konstanz.de
3. and removing all these domains from the transport table.

But I read in sample-smtpd.cf:

# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction, in the description of the
# smtpd_recipient_restrictions parameter.

and

# permit_mx_backup: accept mail for sites that list me as MX host.
# Use the optional permit_mx_backup_networks parameter to also
# require that the primary MX hosts match a list of network
# blocks.

now I'm confused:

The bastions are primary mx for uni-konstanz.de. Do I have to use the
transport or does this note only cover smtpd_receipient_restrictions
--
Jörg Friedrich

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]