OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: RE: Postfix and Exchange, oh joy
From: Peņa, Botp (botpdelmonte-phil.com)
Date: Sat Sep 23 2000 - 02:30:57 CDT

you do not need transport maps. just use the aliases.

btw, if your aliases file for all users is the same as what you've shown,
then mail indeed would NOT bounce since they are routed to exchange

-----Original Message-----
From: Malcolm Tester [mailto:MTestercambric.com]
Sent: Saturday, September 23, 2000 12:12 AM
To: postfix-userspostfix.org
Subject: RE: Postfix and Exchange, oh joy

True. I use transport_maps with

cambric.com smtp:[exchangeserver]
.cambric.com smtp:[exchangeserver]
localhost.cambric.com local:

If I turn that off though, then the two Postfix installations start looping
the mail through each other until it reaches max_hops. If I add the
local_recipient_maps, nothing changes. If I turn off the transport_maps and
leave on the local_recipient_maps, I get the looping problem still.

Is there a way to forward incoming mail for known local users without using
the transport_maps? If not, then is there another way to bounce unknown
users on the middle postfix install before it gets to exchange?

To also answer other questions about the configuration:

"postconf -n":
alias_database = dbm:/opt/postfix/etc/aliases
alias_maps = dbm:/opt/postfix/etc/aliases
canonical_maps = dbm:/opt/postfix/etc/canonical
command_directory = /opt/postfix/sbin
daemon_directory = /opt/postfix/libexec
debug_peer_level = 2
default_destination_concurrency_limit = 10
default_transport = smtp
double_bounce_sender = double-bounce
empty_address_recipient = MAILER-DAEMON
home_mailbox = Mailbox
hopcount_limit = 50
local_destination_concurrency_limit = 2
local_recipient_maps = $alias_maps unix:passwd.byname $relocated_maps
mail_owner = postfix
mail_spool_directory = /var/mail
masquerade_domains = cambric.com
masquerade_exceptions = root
mydestination = $myhostname, localhost.$mydomain
myhostname = amazon.cambric.com
mynetworks = 192.168.1.0/28, 192.168.10.0/28, 127.0.0.0/8, 192.168.1.38/32
myorigin = $mydomain
queue_directory = /var/spool/postfix
relay_domains = exchangeserver.$mydomain, www.$mydomain, ftp.$mydomain
$mydomain
relayhost = 192.168.1.36
relocated_maps = dbm:/opt/postfix/etc/relocated
smtpd_banner = $myhostname ESMTP $mail_name
smtpd_etrn_restrictions = permit_mynetworks
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
sun_mailtool_compatibility = yes
transport_maps = dbm:/opt/postfix/etc/transport

Example user:
On the outmost Postfix install, there are no local users.
On the internal Postfix, there is a local user, "mtester". In the aliases
file, we see
...
root: mtester
postmaster: mtester
mtester: mtesterexchangeserver

On the Exchange server, we have a user, "mtester". His email addresses are:
mtesterexchangeserver.cambric.com (smtp)
mtestercambric.com (smtp)

The version of Exchange is 5.5, SP2.

-> -----Original Message-----
-> From: wietseporcupine.org [mailto:wietseporcupine.org]
-> Sent: Thursday, September 21, 2000 6:04 PM
-> To: postfix-userspostfix.org
-> Subject: Re: Postfix and Exchange, oh joy
->
->
-> Malcolm Tester:
-> > whether the user locally exists or not. For example.
-> With Sendmail, if a
-> > user didn't locally exist, or there was no entry in the
-> aliases file for it,
-> > the mail bounced then and there. Now, it sends it on
-> through to the
-> > Exchange server, which then bounces it, but I'd prefer it
-> to bounce at the
-> > first phase. I tried using the relocated_maps to do so,
-> but that seems to
-> > be ignored. ideas?
->
-> Postfix bounces non-existent users. You have somehow told Postfix
-> to pass such users on to the exchange machine. luser_relay? transport
-> map?
->
-> Wietse
->