• Part 1 – How to Send SMTP Email Using PowerShell
• Part 2 - How to Add a Message Body to Emails Sent from Scripts
• Part 3 - How to Add a HTML Message Body to Emails Sent from Scripts
• Part 4 - How to Create Formatted HTML Output from Scripts

In this article we’ll take it a step further by adding a HTML message body to an email.

For this to work we’ll be using an System.Net.Mail.MailMessage .NET object. This is basically a message object that can be sent via the SmtpClient .NET object that we used in the previous articles. The benefit of using this object in a script is that it can be used to create HTML email messages.

To create the script we can start with similar variables to last time.

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = "administrator@exchangeserverpro.net"
$messageSubject = "List of Exchange Servers"

Next we create the new MailMessage object using the variables above as the To and From addresses, and then set the message subject as well.

$message = New-Object System.Net.Mail.MailMessage $smtpfrom, $smtpto
$message.Subject = $messageSubject

Now comes the important bit, setting the message body to be HTML.

$message.IsBodyHTML = $true

Now all we need is some HTML content to go into the message body. As an example let’s just get a list of Exchange servers and their server roles.

$message.Body = Get-ExchangeServer | Select-Object Name,ServerRole | ConvertTo-Html

All I needed to do above is run Get-ExchangeServer, pipe the output into a Select-Object command to grab just the server name and roles, and then pipe that into the ConvertTo-Html command.

The final step is to create the SmtpClient object and send the mail message.

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($message)

The result is an email that looks similar to this.

Here is the complete example script.

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = "administrator@exchangeserverpro.net"
$messageSubject = "List of Exchange Servers"

$message = New-Object System.Net.Mail.MailMessage $smtpfrom, $smtpto
$message.Subject = $messageSubject
$message.IsBodyHTML = $true

$message.Body = Get-ExchangeServer | Select-Object Name,ServerRole | ConvertTo-Html

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($message)

As you can see this is a pretty simple technique that can be used to easily create basic HTML email messages.

Related posts:

• How to Send SMTP Email Using PowerShell (Part 2)
• How to Send SMTP Email Using PowerShell (Part 4)
• How to Send SMTP Email Using PowerShell (Part 1)
• Using Test-Mailflow with Exchange 2003 Servers
• How to Set Up an Automated Exchange 2010 Database Backup Alert Email

This article How to Send SMTP Email Using PowerShell (Part 3) is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

• Part 1 – How to Send SMTP Email Using PowerShell
• Part 2 - How to Add a Message Body to Emails Sent from Scripts
• Part 3 - How to Add a HTML Message Body to Emails Sent from Scripts
• Part 4 - How to Create Formatted HTML Output from Scripts

In this article we’ll take a closer look at how you can create the email message body for emails that you are sending via PowerShell.

In the last article I demonstrated a simple PowerShell script for sending emails that contained the following code, using the SmtpClient .NET object .

#
#.SYNOPSIS
#Sends SMTP email via the Hub Transport server
#
#.EXAMPLE
#.\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test"
#

param(
[string]$to,
[string]$subject,
[string]$body
)

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = $to
$messageSubject = $subject
$messageBody = $body

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($smtpFrom,$smtpTo,$messagesubject,$messagebody)

Now let’s build on that example by adding more content to the message body of the emails.

Using Command Output as Email Message Content with PowerShell

When running this script anything that we specify with the -Body parameter will be the message body of the email. It could be a text string, or it could even be the output from another PowerShell command. For example:

[PS] C:\Scripts>.\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "List of Exchange Servers" -Body (Get-ExchangeServer)

The command above would produce an email that looks like this:

Neat trick, but notice how the list of Exchange servers appears as all one string that wraps over two lines? Wouldn’t it be nicer to see the server names displayed in an easier to read list format? Let’s take a look at how you can achieve that.

[PS] C:\Scripts>[string]$emailbody = ""

[PS] C:\Scripts>$servers = Get-ExchangeServer

[PS] C:\Scripts>foreach ($server in $servers) {$emailbody = $emailbody + $server.name + "`r`n"}

[PS] C:\Scripts>.\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "List of Exchange Servers" -Body $emailbody

So what did I do there? Here are the steps I just followed:

1. Declare a variable $emailbody as type string. This will be the variable that is passed to the script to be the message body of the email that gets sent.
2. Used the Get-ExchangeServer cmdlet to retrieve a list of the Exchange servers in the organization into an array of $servers.
3. Looped through the array using the ForEach-Object (abbreviated to “foreach”) cmdlet and appended each server name to the $emailbody string, including (and this is the important part) a carriage return after each server name.
4. Ran the script using the $emailbody variable for the -Body script parameter.

The result is an email that looks like this; much better don’t you agree?

Now this is only a demonstration. In reality you probably aren’t going to want to send yourself an email with a list of your Exchange servers, at least not very often.

However you can use the same techniques I’ve just demonstrated to build scripts that email you any command or script output, such as a list of mailboxes with no storage quotas that you have emailed to yourself automatically each month.

Using File Contents as Email Message Content with PowerShell

Another technique for getting content for the message body of an email sent via PowerShell is to use the contents of a file.

For example, I run continuous pings between certain servers to detect any network interruptions that may be occurring. An entry is written to a log file any time a ping times out. Every day I want to receive an email with the results of the previous day’s ping monitoring, so I can do that using a script like this.

#
#.SYNOPSIS
#Sends daily dropped ping report
#
#.EXAMPLE
#.\Send-DroppedPingReport.ps1
#

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = "administrator@exchangeserverpro.net"
$messageSubject = "Dropped ping report"

[string]$messagebody = ""

$logs = Get-Content C:\Logs\droppedpings.log

foreach ($log in $logs )
{
	$messagebody = $messagebody + $log + "`r`n"
}

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($smtpFrom,$smtpTo,$messagesubject,$messagebody)

This is the same technique that was used earlier to create an array and loop through it to add the carriage returns so that the email is formatted nicely. The main difference is the use of Get-Content instead of Get-ExchangeServer.

As you can see it is very simple to create useful, informative emails that are sent by your PowerShell scripts.

Related posts:

• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 4)
• How to Send SMTP Email Using PowerShell (Part 1)
• Using Test-Mailflow with Exchange 2003 Servers
• How to Set Up an Automated Exchange 2010 Database Backup Alert Email

This article How to Send SMTP Email Using PowerShell (Part 2) is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

• Part 1 – How to Send SMTP Email Using PowerShell
• Part 2 - How to Add a Message Body to Emails Sent from Scripts
• Part 3 - How to Add a HTML Message Body to Emails Sent from Scripts
• Part 4 - How to Create Formatted HTML Output from Scripts

There are a few different ways to do this, depending on the version of PowerShell installed on your computer or server. You can check the version number by typing $host in a PowerShell window.

PowerShell 1.0 will show this result:

PS C:\> $host

Name             : ConsoleHost
Version          : 1.0.0.0

PowerShell 2.0 will show this result:

PS C:\> $host

Name             : ConsoleHost
Version          : 2.0

Let’s take a look at how we can send SMTP email using each version of PowerShell.

Sending SMTP Email with PowerShell 1.0

For PowerShell 1.0 we can send mail by running these commands.

PS C:\> $smtp = New-Object Net.Mail.SmtpClient("ho-ex2010-caht1.exchangeserverpro.net")
PS C:\> $smtp.Send("reports@exchangeserverpro.net","administrator@exchangeserverpro.net","Test Email","This is a test")

So what did we just do there? Let’s break it down.

1. Created a new instance of a .NET object of class SmtpClient, connected to the SMTP server ho-ex2010-caht1 (a Hub Transport server)
2. Used the Send method of the object to send an email message with the following:
• From address of “reports@exchangeserverpro.net”
• To address of “administrator@exchangeserverpro.net
• Subject of “Test Email”
• Body of “This is a test”

That works fine, though perhaps a bit cumbersome to type it out every time. Instead what we could do is create a script to send SMTP email using PowerShell 1.0.

#
#.SYNOPSIS
#Sends SMTP email via the Hub Transport server
#
#.EXAMPLE
#.\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test"
#

param(
[string]$to,
[string]$subject,
[string]$body
)

$smtpServer = "ho-ex2010-caht1.exchangeserverpro.net"
$smtpFrom = "reports@exchangeserverpro.net"
$smtpTo = $to
$messageSubject = $subject
$messageBody = $body

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($smtpFrom,$smtpTo,$messagesubject,$messagebody)

We can save that code as Send-Email.ps1 and run it from the PowerShell window.

PS C:\Scripts> .\Send-Email.ps1 -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test"

Less typing required, especially when you hard-code some of the variables such as the From address and SMTP server.

Sending SMTP Email with PowerShell 2.0

PowerShell 2.0 makes life a little easier thanks to the built in cmdlet Send-MailMessage. To send the same email as the above example we would run this command:

PS C:\> Send-MailMessage -From "reports@exchangeserverpro.net" -To "administrator@exchangeserverpro.net" -Subject "Test email" -Body "This is a test email"

One of the first things you might notice in the command above is that no SMTP server was specified. Send-MailMessage does have a -SmtpServer parameter, but if you don’t specify one it will just use the $PSEmailServer preference variable instead. This can be set for the session by running the following command:

PS C:\> $PSEmailServer = "ho-ex2010-caht1.exchangeserverpro.net"

Another point to note with Send-MailMessage is that is uses authenticated SMTP connections. By default it will use the credentials of the user executing the command. So you need to make sure you’re using an SMTP server that either:

• Permits that authenticated user credential to send email messages via SMTP
• Accepts anonymous SMTP/relay for the IP address of the sending host (you can see how to configure a relay connector for Exchange here)

Those are just a few simple examples of how to send email using SMTP and PowerShell 1.0 or 2.0.

Related posts:

• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• Using Test-Mailflow with Exchange 2003 Servers
• How to Set Up an Automated Exchange 2010 Database Backup Alert Email
• PowerShell Script: Check Exchange 2010 Database Backups

This article How to Send SMTP Email Using PowerShell (Part 1) is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

This is useful both for internal and external email messages. In one recent real world example we used message headers to diagnose which hop along the email route was causing large delays for emails into the organization.

To view the message headers in Outlook 2010 click on the arrow next to Tags in the ribbon menu.

To view the message headers in Outlook 2007 click on the arrow next to Options in the ribbon menu.

The message options will appear with the header information towards the bottom.

I usually find it easier to copy the header text into Notepad for viewing.

So let’s take a look at some of the header information that is useful to us. First there is the basic information about the email message itself.

Then there are the email servers that the message passed through on it’s way to the destination. To follow these in order start at the bottom and read upwards.

These lines are generally in the following format:

Received: from servername (IP address) by servername (IP address) with MTA-name; timestamp

When a message passes over several hops this can get a bit confusing to read. So I like to break out each entry and tidy them up into a readable format. I usually get something more like this:

1. ironport1-mx.cbr1.mail-filtering.com.au (203.88.115.241) -> HO-EX2010-CAHT1.exchangeserverpro.net (10.1.1.14); Mon, 19 Sep 2011 19:41:57 +1000

2. ju001lcs02.dfw.the-server.net.au ([175.107.191.11]) -> ironport1-mta.cbr1.mail-filtering.com.au with ESMTP; 19 Sep 2011 19:41:43 +1000

3. [209.85.213.177] (helo=mail-yx0-f177.google.com) -> ju001lcs02.dfw.the-server.com.au; Mon, 19 Sep 2011 19:41:42 +1000

4. yxi11; Mon, 19 Sep 2011 02:41:38 -0700 (PDT)

5. 10.68.5.133; Mon, 19 Sep 2011 02:41:38 -0700 (PDT)

6. 10.68.43.230; Mon, 19 Sep 2011 02:41:38 -0700 (PDT)

To me that is just more readable. You can take it a step further by converting timestamps into the same time zone, which makes it a little easier to identify any major delays as the message was transmitted between servers.

As you can see by learning to view and understand message headers you gain a much deeper understand of how email messages are flowing between senders and recipients, which will help you a lot during troubleshooting situations.

Related posts:

• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• How to Send SMTP Email Using PowerShell (Part 1)
• Email Fundamentals: How to Send Email via Telnet
• Resolving Anonymous Mail to the GAL with Exchange Server 2010

This article Email Fundamentals: How to Read Email Message Headers is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Let’s say you’ve just configured a relay connector and want to test it from the server that you wish to allow relay from before you let that server’s owner know that it is all set up for them. Or perhaps you want to quickly test whether a another email server on the internet is accepting mail from your network.

For just about any scenario where you want to quickly test SMTP knowing this method is very useful.

Note: this technique requires the Telnet client to be installed on the computer you’re running the test from. For Windows XP and Windows Server 2003 it will already be installed, but Windows 7 and Windows Server 2008 need to install it first.

Installing the Telnet Client for Windows 7

To install the Telnet client on a Windows 7 computer use these steps.

1. Open the Control Panel
2. Click on Programs
3. Click on Turns Windows Features on or off
4. Scroll down the list until you see Telnet Client, and tick that box
5. Click OK and close the Control Panel

Installing the Telnet Client for Windows Server 2008

To install the Telnet client on a Windows Server 2008 computer open a command prompt and run the following command.

C:\>servermanagercmd -i telnet-client
.........

Start Installation...
[Installation] Succeeded: [Telnet Client].

Success: Installation succeeded.

Installing the Telnet Client for Windows Server 2008 R2

To install the Telnet client on a Windows Server 2008 R2 computer open a PowerShell window and run the following command.

PS C:\> Import-Module servermanager
PS C:\> Add-WindowsFeature telnet-client

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    No             Success   {Telnet Client}

Sending Email from the Command Line via Telnet

Open a command prompt and use Telnet to connect to the remote email server on port 25.

C:\>telnet esp-ho-ex2010a 25

If Telnet is able to connect to the remote server you should see its welcome banner.

220 ESP-HO-EX2010A.exchangeserverpro.net Microsoft ESMTP MAIL Service ready at T
ue, 9 Aug 2011 22:00:04 +1000

The first command to send is the HELO command. Some email servers will accept HELO on its own, others will require you to also provide a host or domain name along with it.

helo test.com
250 ESP-HO-EX2010A.exchangeserverpro.net Hello [10.0.1.11]

Next use the MAIL FROM command to tell the remote server who the email is from.

mail from: test@test.com
250 2.1.0 Sender OK

Now use the RCPT TO command to tell the remote server who to deliver the email to.

rcpt to: alan.reid@exchangeserverpro.net
250 2.1.5 Recipient OK

The final step for the bare minimum set of commands is the DATA command.

data
354 Start mail input; end with .

If you just want to send a blank message type a period “.” and press enter. Otherwise you can set a subject line for the message if you like. Use SUBJECT and then type your subject line, and press enter.

subject: this is a test message

Type any text you want to include with the message, press enter, and then finally type a period “.” and press enter to send the email.

sending a test message via telnet
.
250 2.6.0  [InternalId=320] Queued mail for delivery

If the message was queued for delivery then it has been accepted by the server. If this is an Exchange server that you control then you can use message tracking to troubleshoot further if the message doesn’t make it to the inbox that you were expecting.

Type the QUIT command to terminate the connection when you’re done.

SMTP Status Codes

You may notice along the way that after typing commands you see responses from the server starting with “250″.

250 is a good thing, and there are a lot of other SMTP status codes you’ll encounter the more you use this technique. For example an email server may deny your attempt to relay mail between two domains.

550 5.7.1 Unable to relay

Or you may encounter an email server that is explicitly blocking email from your domain.

554 5.1.0 Sender denied

There are a lot of different scenarios you might encounter here, and thankfully the SMTP status codes will help you troubleshoot them.

Now that you understand how to send email using Telnet and the command line I hope you find this technique very useful in the future.

Related posts:

• Install telnet on Windows Server 2008
• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• How to Send SMTP Email Using PowerShell (Part 1)
• Email Fundamentals: How to Read Email Message Headers

This article Email Fundamentals: How to Send Email via Telnet is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

In this scenario you may encounter an issue where the emails that end users receive show the SMTP address of the sender instead of the more friendly display name configured on the user mailbox that has that SMTP address.

For example an email from a scanner device will appear like this.

This will occur if the Receive Connector on the Hub Transport server is accepting anonymous email. Receive Connectors are not configured this way by default but many Exchange administrators enable it because it is the simplest way to allow applications or devices to send emails to internal recipients.

To enable Exchange Server 2010 to resolve the anonymous emails you need to configure the Authentication settings for the Receive Connector to enable the Externally Secured option.

However this is not possible for the Default Receive Connector due to the other Authentication settings that are already enabled.

Instead what you can do is create a relay connector for Exchange Server 2010 following the instructions here. Whether you restrict it to certain sender IP’s or allow your entire private network to use the relay connector is up to you.

Emails sent from devices using the new Receive Connector will resolve the name correctly from the GAL now.

Related posts:

• How to Migrate a Relay Connector from Exchange Server 2007 to 2010
• How to Configure a Relay Connector for Exchange Server 2010
• Avoiding Infinite Loops with Internal Relay Domains in Exchange 2007/2010
• Review of CodeTwo Exchange Rules Pro
• Exchange 2007/2010 Transport Rule Logging

This article Resolving Anonymous Mail to the GAL with Exchange Server 2010 is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Link: Microsoft Certified Master Video: Exchange 2010 Header Firewall

Related posts:

• TechEd Video: Exchange Server 2010 High Availability Deep Dive
• TechEd Video: Exchange Server 2010 High Availability Concepts
• Avoiding Infinite Loops with Internal Relay Domains in Exchange 2007/2010
• Exchange Server 2010 Training
• Free Exchange Server Technical Education Videos

This article Microsoft Certified Master Video: Exchange 2010 Header Firewall is © 2011 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

It has been my experience that no matter how well managed or documented an environment is, there is always some application or device that nobody thinks of that is relaying email through the Exchange server.  Whether its a custom app that some developer is running on his workstation, or a printer that does scan-to-email, something is bound to break when you remove the Exchange server.

Fortunately you can just about eliminate this risk with a little log monitoring on the Exchange 2003 server.  This is best performed after you have migrated all data and known services away from the server, to minimise the amount of potential traffic you pick up in the monitoring.

The first step is to enable logging of SMTP traffic on the server.  Open Exchange System Manager and navigate to the SMTP Virtual Server.

Open the properties of the SMTP Virtual Server.  Tick the box to enable logging.

Leave the log format as “W3C Extended” and click the Properties button.  Take note of the log file directory, and I also always enable local time for log naming and rollover

Click on the Advanced tab and enable at a minimum the Client IP Address.  I also include the Date and Time, and depending on your environment there may be other extended properties that you should enable.

Click OK, OK, etc to apply the new configuration.  You can now wait for as long as you deem necessary to capture any remaining SMTP traffic that is traversing the server.  I aim for 48 hours but in some environments a longer period would be appropriate.

Once the logging has been enabled and allowed to run for a while you’ll have one or more log files in the log file directory.

If you look in a log file you’ll see a list of IP addresses that have connected to the server for SMTP.  A typical SMTP session will generate more than one line of logging, so this means potentially hundreds or thousands of lines of logging, maybe over multiple log files, that need to be consolidated down into a list of unique IP addresses.

This consolidation is made easy thanks to Logparser.  Download and install Logparser, and then launch it from the Start Menu.

A very simple query to extract the unique IP addresses from the SMTP log files looks like this:

C:\Program Files\Log Parser 2.2>LogParser -i:IISW3C "SELECT DISTINCT c-ip FROM 'C:\WINDOWS\system32\LogFiles\SMTPSVC1\*.*'"
------------
192.168.0.2
192.168.0.101
192.168.0.110

Statistics:
-----------
Elements processed: 8181
Elements output:    3
Execution time:     0.09 seconds

You have now got a nice short list of IP addresses that are using the server for SMTP communications and can go and investigate the applications or device configs that are causing it, before you shut down the legacy servers for good.

Related posts:

• Exchange Server 2010 SP1 Mailbox Audit Logging Step by Step Guide
• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• How to Send SMTP Email Using PowerShell (Part 1)
• Email Fundamentals: How to Read Email Message Headers

This article Check Your Legacy Exchange Servers for SMTP Usage Before Removing Them is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Configure the Receive Connector

To allow the Exchange server to accept incoming email from the internet the default Receive Connector must be modified.  Navigate to Server Configuration/Hub Transport.  Open the properties of the default Receive Connector.

Select the Permission Groups tab and enable the Anonymous Users group.  Click OK when complete.

Configure the Send Connector

Navigate to Organization Configuration/Hub Transport.  In the Actions pane to the right of the Exchange Management Console click New Send Connector.

Enter a meaningful name such as Internet Email and set the intended use to Internet.

Click Next to continue.

Click the Add button and add an SMTP address space of * to route all mail to external domains over this Send Connector.

Click OK and then Next to continue.

If you route your outgoing mail via an ISP smart host or email security service choose that option and enter the IP address or DNS name of the smart host.  You can add more than one smart host if necessary.  Otherwise leave it configured to use DNS to route mail directly to the destination.

Click Next to continue.  The Hub Transport server is automatically included as a source server for the Send Connector.  Click Next to continue, then New to create the Send Connector with the chosen settings.  When the Send Connector has been created successfully click Finish.

Allow the Exchange Server 2007 server to send email to the internet

Add a rule on your network’s firewall to permit the Exchange Server 2007 server to send traffic to the internet on TCP port 25.  On an ISA Server 2006 firewall the process is as follows.

Open the ISA Server Management console and navigate to <ISA server name>/Firewall Policy.

Click on Create Access Rule in the Tasks pane on the right side of the ISA Server Management Console.

Give the new Access Rule a meaningful name such as “Permit Outbound SMTP”.  Click Next to continue.

Set the Rule Action to Allow.  Click Next to continue.

Leave the Protocols set to “Selected protocols”.  Click the Add button and choose SMTP from the Common Protocols list.  Click Add again to add SMTP to the list of permitted protocols for this Access Rule.

Click Close to close the Add Protocols selection dialog, then click Next to continue.

For the Access Rule Sources click the Add button and then click New -> Computer.

Enter the name and IP address of the Exchange Server 2007 server then click OK.

In the Add Network Entities dialog navigate to Computers and select the computer object you just created.  Click Add to add it to the new Access Rule, then click Close.

Now that the Exchange server is showing in the list of Access Rule Sources click Next to continue.

In the Access Rule Destinations dialog click Add, navigate to Networks select External then click Add and Close.  Click Next to continue.

Leave the User Sets configured to All Users.  Click Next to continue, then click Finish to close the New Access Rule Wizard.

Apply the ISA rule changes.

Related posts:

• Publish incoming SMTP to the Exchange Server 2007 server with ISA Server 2006
• How to Share an Email Domain Between Two Mail Systems
• Route outbound email through the Exchange Server 2007 Hub Transport server
• Publish Exchange Server 2007 OWA Using ISA Server 2006
• Avoiding Infinite Loops with Internal Relay Domains in Exchange 2007/2010

This article Configuring the Exchange Server 2007 Hub Transport Server is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

C:\>servermanagercmd -i telnet-client
.........

Start Installation...
[Installation] Succeeded: [Telnet Client].
<100/100>

Success: Installation succeeded.

Related posts:

• Email Fundamentals: How to Send Email via Telnet
• Windows Server 2008 ServerManagerCMD.exe command reference
• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)
• How to Send SMTP Email Using PowerShell (Part 1)

This article Install telnet on Windows Server 2008 is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com