All you need is a spare public IP and NAT it to your HT server. I prefer not using an Edge server if you are sending all outbound emails to FOPE since your networking team will have an ACL on the firewall allowing only your HT server SMTP access to the FOPE subnet.
Sent from my iPhone On Mar 18, 2013, at 8:58 AM, "Alexander Rose" <arose...@gmail.com> wrote: > Hi all, > > We currently use an old Anti-Spam appliance as our smart host, it is located > in a DMZ and has a NATed IP for sending emails to the outside world. We only > have one Send Connector in our Exchange Org. and it uses this smart-host for > all emails. > > > I have created a new send connector to test our new smart-host > (mail.messaging.microsoft.com as were moving to FOPE). > After an email was sent for testing, i received a notification from Microsoft > that states that the IP used to send the email was blocked and banned. When i > checked the IP, i found out it is the one our internal clients are getting > when they go on Internet (if i go to whatismyip.com from my workstation i get > that IP, all clients are NATed to that one public IP). > > As all our clients are using this IP, we would like to use a dedicated public > IP for sending emails. In our situation the only solution i see would be to > setup our own smart-host first (let say a Edge Sync Server), create a default > send connector on our Exchange HUBs to direct emails to this Edge Sync server > and create another Send connector on the Edge Sync server to direct emails to > FOPE. > > Am i correct? Or is there a way to do differently? > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
