Actually, I think he needs transport maps. They allow you to define a forward for each domain, where as relay host basically says if you don't know what to do send it here.
Quote:
# TRANSPORT(5) TRANSPORT(5)
#
# NAME
# transport - Postfix transport table format
#
# SYNOPSIS
# postmap /etc/postfix/transport
#
# postmap -q "string" /etc/postfix/transport
#
# postmap -q - /etc/postfix/transport <inputfile
#
# DESCRIPTION
# The optional transport(5) table specifies a mapping from
# email addresses to message delivery transports and/or
# relay hosts. The mapping is used by the trivial-rewrite(8)
# daemon.
#
# This mapping overrides the default routing that is built
# into Postfix:
...
|
open /etc/postfix/transport in your favorite editor scroll to the bottom and add line like this:
Quote:
domain1.com smtp:exchange1.mydomain.local
domain2.com smtp:exchange2.mydomain.local
|
next run:
Quote:
|
postmap /etc/postfix/transport
|
reload postfix and you should be ready.
Now for a couple of notes.
If your exchange server is sending mail out, please use a real domain and not .local otherwise you may have problems with mail being blocked RFCs require you to use a valid domain name.
If your exchange servers are forwarding outgoing mail to the postfix server, this shouldn't be a problem as long as postfix has a valid domain name.
Personal comment:
Quote:
|
exchange YUK! (Sorry, hard core Groupwise man here.) My Groupwise server was up for 3 years with ZERO downtime, until a prolonged power outage took the server down. Just can't do that with exchange.
|
