On Thu, May 2, 2013 at 9:12 PM, Richard Stovall <[email protected]> wrote: > (That said, the original request for a port reference document seems > extremely reasonable. The fact that one will not be made available is, > well, bizarre.)
The usual explanation is that Exchange requires so many ports and services that trying to punch holes through a firewall for it defeats the purpose. And there's something to be said for that. If you have a firewall that allows just about every service you're running through it, and then only block all the ports you're *not* using in the first place, you're really missing the point. But I also can't help but wonder if Microsoft has just lost track of all the ports Exchange might use. :-) -- Ben --- To manage subscriptions click here: or send an email to with the body: unsubscribe exchangelist
