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 with Internal MS Exchange
From: Pena, Botp (botpdelmonte-phil.com)
Date: Sun Sep 10 2000 - 23:33:59 CDT


rick,

we have more or less the same setup. you could actually examine the internal
header of this mail and find that our internal exchange server is routing
mails to external postfix server (and vice versa).

i didn't have to place mx records for my exchange. only the postfix has the
mx. it (the postfix) just routes the mail to our internal exchange servers
(i just placed the IN Address in the db dns). the internal exchange server
also routes it's mails to the postfix (under IMS, select route to host, note
i am not even using dns on my exchange ;-).

i then used the $aliseses file to route mails for the exchange users (this
is the most critical). in our network here, not all exchange users are
internet mail users.

then i just placed the network addresses (where my exchange servers are
located) in $mynetworks. that's all (and it's that simple ;-)

i actually transferred from sendmail to postfix for just under 30
minutes(kudos to wietse). the postfix-exchange tandem just rocks!

cheers,
-botp

> -----Original Message-----
> From: Rick Cogley [mailto:rick.cogleyesolia.co.jp]
> Sent: Thursday, September 07, 2000 5:03 PM
> To: 'postfix-userspostfix.org'
> Subject: Postfix with Internal MS Exchange
>
>
> Greetings -
>
> I am sorry for the newbie question, but I am at a loss even
> after having
> read the redhat postfix faq and postfix.org faq - I hope
> someone can help.
>
> Unfortunately, the domains I have won't go live for another
> couple of days,
> so it is hard to test what I have.
> So I would like to bounce my ideas off someone to make sure
> what I am doing
> is correct.
>
> Your help is greatly appreciated.
>
> CURRENT
> * Running Redhat 6.2 firewall set up with postfix, and the
> box is set to
> listen on port 25 - confirmed by netstat and telnetting to
> port 25 of the
> firewall.
> * Postfix seems to have installed correctly, and starts with
> no errors.
> * Running NT with Exchange inside, and Exchange is listening
> on port 25, and
> is set up for two domains "something.org" and "theother.org".
> * DNS set up to point MX of the two domains at IP address of
> firewall w/
> postfix.
> * Confirmed that I can send mail from Exchange box, via Outlook.
> * Confirmed that I can send mail from Firewall, via command
> such as # cat
> myfile | mail rick.cogleyesolia.co.jp
> * Have /etc/hosts file on firewall set up to allow it to
> resolve Exchange IP
> address (NATtted 192.168.x.x address). I.e. 192.168.0.x ntexsrv
> * My main.cf looks like this -
>
> myhostname = gw1.something.org
> mydomain = something.org
> alias_maps = hash:/etc/postfix/aliases
> masquerade_domains = $mydomain
> masquerade_exceptions = root
> transport_maps = hash:/etc/postfix/transport
>
> * My /etc/postfix/transport looks like -
> something.org :[192.168.0.x]
> .something.org :[192.168.0.x]
>
> GOALS
> I would like to have the following happen -
>
> 1. Use postfix as the main mx for my domains "something.org" and
> "theother.org".
> 2. Forward mail into my exchange server for receipt by users.
> The exchange
> is now set up to receive mail on "something.org" and "theother.org".
> 3. Queue mail for the two domains when (not if) Exchange goes
> down, and send
> the queued mail to exchange when it comes back up.
> 4. For regular mail aliases like root, forward the mail
> inside to an admin
> address in Exchange.
>
> QUESTIONS
> * Is there something simple I can do to make this work? I
> have looked at
> various docs, some excerpts below, but I
> still don't have a clear understanding of how it all fits.
> (Though I must
> say it is much clearer than sendmail!)
> * Since the domains are real ones, can I put multiple addresses on the
> relevant lines? Like this -
>
> * Edited main.cf - is this 'legal' postfix?
>
> myhostname = gw1.something.org gw1.theother.org
> mydomain = something.org theother.org
> alias_maps = hash:/etc/postfix/aliases
> masquerade_domains = $mydomain
> # ----or, do I need to make another symbol like $mydomain2 , and do:
> # ----masquerade_domains = $mydomain $mydomain2
> masquerade_exceptions = root
> transport_maps = hash:/etc/postfix/transport
>
> * Edited /etc/postfix/transport -
> something.org :[192.168.0.x]
> .something.org :[192.168.0.x]
> theother.org :[192.168.0.x]
> .theother.org :[192.168.0.x]
>
>
>
> ------------------------excerpts------------------------
> #mydestination = $myhostname, localhost.$mydomain
> #mydestination = $myhostname, localhost.$mydomain $mydomain
> #mydestination = $myhostname, localhost.$mydomain, $mydomain,
> # mail.$mydomain, www.$mydomain, ftp.$mydomain
>
> # The mailbox_transport specifies the optional transport in master.cf
> # to use after processing aliases and .forward files. This parameter
> # has precedence over the mailbox_command, fallback_transport and
> # luser_relay parameters.
> #
> #mailbox_transport = cyrus
>
> # 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 file sample-smtpd.cf.
> #
> #relay_domains = $mydestination
>

===========================================
Del Monte Philippines, Inc (Bugo, Cagayan de Oro City)