How do I set the Source IP for a Send Connector on a Hub Transport server? If this were an Edge Transport server then I'd simply run "set-SendConnector 'Outbound' -SourceIPAddress xx.xx.xx.xx" - but the documentation explicitly states "This parameter is only valid for Send connectors that are configured on Edge Transport servers." Background: I'm receiving errors from server's like Comcast due to improperly configured reverse DNS settings (example). Easy fix. The problem is that the server has multiple IP addresses and Exchange 2007 is sending mail out via an IP not bound to the host name it introduces itself as (mail.domain.tld). Alternative: Is there a way to tell Exchange Server 2007 to only bind itself to particular IPs? In this case, the IP associated with mail.domain.tld?I'm hoping this is an easy issue! But I'm having trouble finding a solution. Jeremy

The article Deployment Options for Hub Transport Servers confirms the issue: "If you configure an Internet-facing Hub Transport server, you cannot configure a Send connector to attach a particular IPaddress to messages that are sent from the Hub Transport server. For example, if more than one IPaddress is assigned to the Hub Transport server, you cannot select which IPaddress is used by a Send connector to relay e-mail to the Internet. If you use an SMTP relay, such as an Edge Transport server, the IPaddress of that computer is affixed as the message source." Is there a work around for this? Is there a way to limit the IP addresses assigned to the Hub Transpor server role without removing those IP addresses from the server itself?

Any thoughts on this?KB948505 additionally notes "The concept of a primary IP address does not exist in Windows Vista or in Windows Server 2008" which further limits possible work arounds. The only solution I can think of is to a) setup an Edge Transport (not needed for our size organization) or b) move extra IPs (and, thus, services that depend on them) to another machine. The latter is within our Q2 plans anyway but this seems like a ridiculous limitation?Maybe there's a routing hack for outbound port 25 traffic? Anyone?

Hi,Indeed, that is by design.I will pass on your feedback to our PG. Maye we you can use the third party smart host or set up own smart host to deliver your email. Such as Postini.Additionally, below article is the instruction of setting up SMTP service on separate computer for relay the email:http://www.petri.co.il/configure_iis_to_be_a_smart_host_for_exchange.htmThanksAllen

What's bizarre about the limitation to me is that it's not a restriction of the Edge Transport Server. For now, the "random" outbound IP has been stable and so we've been able to setup a temporary rDNS mapping to it to get around the issue - at least until we setup another server with fewer services (i.e., that will only require a single IP). As for passing on feedback to the PG: thanks. I think the core issue here is that while Exchange has always been optimized for an enterprise environment, Exchange 2007 is the first to be particularly restrictive for a small business environment. And yet, despite that, as seen on forums and blogs, there are a lot of small businesses that still choose to go with the stand-alone version as opposed to the more integrated Small Business Server - either because they're unaware of SBS or because, like me, they have some preference for purchasing and configuring invidiual products.