In theory, I get it. Forgive my stupidity, but I've never had to configure a second IP. Is it as simple as Adding a second address in the Advanced TCP/IP properites? Then, would that IP resolve to an addtional MX record or just a normal host record? (it will only be used internally)
Currently we have mail.domain.com (MX) that resolves to our primary IP on the Hub Transport. The big question - it appears this would not require a downtime - am I correct with this assumption? On Wed, Apr 9, 2008 at 3:47 PM, Michael B. Smith < [EMAIL PROTECTED]> wrote: > I use another IP address and bind it to the additional connector. > > > > Regards, > > > > Michael B. Smith > > MCSE/Exchange MVP > > http://TheEssentialExchange.com > > > > *From:* Angie Urtel [mailto:[EMAIL PROTECTED] > *Sent:* Wednesday, April 09, 2008 2:34 PM > *To:* MS-Exchange Admin Issues > *Subject:* additional receive connector for anonymous > > > > My organization has an additional (3rd) Receive Connector for Internal > Hosts that need to relay SMTP. This connector allows Anonymous connections > from certain IPs. The default Receive Connector is not setup for Anonymous > access. > > My issue is - we have an application that is in the IP list for the > Internal Hosts connector, but is routing (and getting blocked because its > not authenticated) through the default connector. What is the > procedure/rules/flow to get some machines to use this additional connector? > As far as I know, this is the first time it has not worked. > > The application is setup to use a generic DNS name for the Hub Transport > server. I see the IP in the SMTP Receive logs, initiating a connection with > the wrong connector. > > All of the articles I find just say to allow Anonymous on the Default > Connector, which I don't want to do. Any tips? > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
