Discussion on:

Configuring Exchange 2007 to be an Edge Transport Server

Colleagues who support MS Exchange acknowledge it is a challenging task.

The functionalities provided by MS Exchange in this role has been there for a while using a combination of a SMTP server (postfix/qmail/exim ...), ClamAV, spamassassin etc.

Just wondering why bear the cost of an additional Exchange "Edge Transport Server" when cost effective alternatives are available.

I'm wondering the same thing myself: why license an additional Exchange server when there are viable hardware (and software) alternatives on the market?

The only benefit I can think-of would be the ability to run MS ForeFront on the ETS, rather than the Domain Exchange server...

Can someone provide greater insight on this topic?

Hi,

Heard that lisences for Server Core 2008 costs less, will this "role specific" exchange have something similar????

Question from a student:

what is the impact of removing emails with an Edge server on the Electronic Legal Side, especially on archiving?

Good Article

Great article. The proper syntax is

New-EdgeSubscription -FileName "C:\EdgeServerSubscription.xml"

Thx.

On the part where you do the New-EdgeSubscription command, you posted incorrectly, it should be New-EdgeSubscription -file c:\subscription.xml. Thanks for posting this though, it's been very helpful.

AS many guys are saying when there is good option of MS exchange server then why one will use "Edge Transport server"?