Exchange 2003 Setup and configuration

Guide
First install two servers running Windows 2003 (R2 if you have it)

Next patch fully using Windows update

Create a domain controller (any therefore a domain)

Join the second machine to the domain

On the second machine which will become your Exchange server install the prereqs for Exchange

Open Add/Remove Programs control panel

Click Add/Remove Windows Components

Select Application Server and click Details

Click ASP.NET
Double Click Internet Information Services (IIS)

Scroll down and check the box next to NNTP and SMTP

Click OK twice and then click Next

When prompted insert the CDs as requested

Once the install is complete click Finish and close the Add/Remove programs control panel

Exchange install - Forest and Domain Prep

Next insert the Exchange 2003 CD

Click Exit on the first page

Now download the latest Exchange deployment tools which can be found at the link below (as of 30/12/2006)

http://www.microsoft.com/downloads/details.aspx?familyid=271e51fd-fe7d-42ad-b621-45f974ed34c0&displaylang=en

Once you have the latest Exdelpoy.exe double click it.

Enter the location to save the files and click "OK"

Click OK
Next locate and double click the exdeploy.hta file

You are now at the first page of the Exchange deployment tools

Click "Deploy the first Exchange server"

Click "New Exchange 2003 Installation"

The first three steps are all about ensuring the prerequisites are met. Select the checkboxes by steps 1 and 2 as these have
already been covered.
Select the checkboxes by steps 1 and 2 as these have already been covered.

For step three ensure the support tools are installed. If they are not, download them from the link below and install them:

http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
Click the box by step three

To perform step four open a CMD prompt (Start, Run, type "CMD", Press "Enter")

In the CMD prompt window type the command below and press enter:

dcdiag /f:c:\dcdiaglog.txt /s:domaincontrollername.domain.com

This will output the results to a text file in the C: called dcdiaglog.txt. Open the file and ensure there are no errors. You should see
output like the following:

Domain Controller Diagnosis

Performing initial setup:

Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\E2K7DC1

Starting test: Connectivity

......................... E2K7DC1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\E2K7DC1

Starting test: Replications

......................... E2K7DC1 passed test Replications

Starting test: NCSecDesc

......................... E2K7DC1 passed test NCSecDesc

Starting test: NetLogons

......................... E2K7DC1 passed test NetLogons

Starting test: Advertising

......................... E2K7DC1 passed test Advertising

Starting test: KnowsOfRoleHolders

......................... E2K7DC1 passed test KnowsOfRoleHolders

Starting test: RidManager

......................... E2K7DC1 passed test RidManager

 Starting test: MachineAccount

......................... E2K7DC1 passed test MachineAccount

Starting test: Services

......................... E2K7DC1 passed test Services

Starting test: ObjectsReplicated

......................... E2K7DC1 passed test ObjectsReplicated

Starting test: frssysvol

......................... E2K7DC1 passed test frssysvol

Starting test: frsevent

......................... E2K7DC1 passed test frsevent

Starting test: kccevent

......................... E2K7DC1 passed test kccevent

Starting test: systemlog

......................... E2K7DC1 passed test systemlog

Starting test: VerifyReferences

......................... E2K7DC1 passed test VerifyReferences

Running partition tests on : ForestDnsZones

Starting test: CrossRefValidation

......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom

......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones

Starting test: CrossRefValidation

......................... DomainDnsZones passed test CrossRefValidation

 Starting test: CheckSDRefDom

......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema

Starting test: CrossRefValidation

......................... Schema passed test CrossRefValidation

Starting test: CheckSDRefDom

......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration

Starting test: CrossRefValidation

......................... Configuration passed test CrossRefValidation

Starting test: CheckSDRefDom

......................... Configuration passed test CheckSDRefDom

Running partition tests on : exchange

Starting test: CrossRefValidation

......................... exchange passed test CrossRefValidation

Starting test: CheckSDRefDom

......................... exchange passed test CheckSDRefDom

Running enterprise tests on : exchange.local

Starting test: Intersite

......................... exchange.local passed test Intersite

Starting test: FsmoCheck

......................... exchange.local passed test FsmoCheck

If you get any errors then investigate them. You could post a question to the forums at http://www.mmmug.co.uk/forum

So long as you have no errors move back to the deployment tools and check the 4th box.

Next move back to the command prompt and enter the command below and press enter:

Netdiag >c:\netdiaglog.txt
The command will take a short while to execute. Once complete view the log file in the C:

...................................

Computer Name: E2K7MB1

DNS Host Name: E2K7MB1.exchange.local

System info : Microsoft Windows Server 2003 R2 (Build 3790)

Processor : x86 Family 6 Model 13 Stepping 8, GenuineIntel

List of installed hotfixes :

KB890046

KB893756

KB896358

KB896422

KB896424

KB896428

KB898715

KB899587

KB899588
KB899589

KB899591

KB900725

KB901017

KB901214

KB902400

KB904706

KB904942

KB905414

KB908519

KB908531

KB909520

KB910437

KB911164

KB911280

KB911562

KB911567

KB911927

KB912919

KB914389

KB916281

KB917344

KB917734

KB917953

KB918439

Q147222
Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : E2K7MB1

IP Address . . . . . . . . : 192.168.23.20

Subnet Mask. . . . . . . . : 255.255.255.0

Default Gateway. . . . . . : 192.168.23.1

Dns Servers. . . . . . . . : 192.168.23.10

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Failed

No gateway reachable for this adapter.

NetBT name test. . . . . . : Passed

[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped

There are no WINS servers configured for this interface.

Global results:

Domain membership test . . . . . . : Passed

NetBT transports test. . . . . . . : Passed

List of NetBt transports currently configured:

NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}

1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.

 You have no connectivity to other network segments.

If you configured the IP protocol manually then

you need to add at least one valid gateway.

NetBT name test. . . . . . . . . . : Passed

[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS'
names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed

Redir and Browser test . . . . . . : Passed

List of NetBt transports currently bound to the Redir

NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}

The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser

NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}

The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Passed

Secure channel for domain 'EXCHANGE' is to '\\E2K7DC1.exchange.local'.

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped

No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully

The text file should like the above output. You should get no errors. (I have errors for Default gateway because this is an isolated
test system)

If you get any errors then investigate them. You could post a question to the forums at http://www.mmmug.co.uk/forum

So long as you have no errors move back to the deployment tools and check the 5th box.

The next step is to run Forest prep. This must be run by a user with Schema administrator permissions. Forest Prep will extend the
AD Schema with the new classes and attributes that Exchange 2003 requires to operate.

To proceed enter the path to the install CD in the box provided and click "Run ForestPrep now"

WARNING: This operation is not undoable. Only do this if you are certain you want to proceed. I suggest testing in a lab
environment before going into production. If you are unsure post a question in the
Forums. http://www.mmmug.co.uk/forum
If prompted about an incompatibility then select the checkbox to ignore the warning in the future and click “Continue”

The Warning occurs because Exchange 2003 RTM needs upgrading to SP2 which we will install later.

Once the install opens click “Next”

Agree to the license and click “Next”

Note that only ForestPrep will be performed and that files will go in the default location C:\Program Files\Exchsrvr (this can be
changed if required to place files on an Application drive)
Click “Next”

Select the account to be the first Exchange Full Administrator. The default is the account you are logged in as. If you are only
logging in as a special schema admin account then you should select an account that will be used to admin Exchange. I will leave
the default in place of Administrator.

Click “Next”

SCREENSHOT of ACCOUNT DETAILS MISSING

ForestPrep is a fairly slow process that could take around 30mins on a slow network. You will see several screens like the one
below
Once the process is complete click Finish
Next move back to the deployment tools and check the box on the 6th step

Now move onto the Domain Prep. This will need to be performed in the root domain and any others which will hold Exchange
mailboxes. Personally it is simplest to run it in all domains in the forest.

In a simple single domain forest proceed as follows:

Enter the path to the Install files where requested and click “Run DomainPrep now”.
On the welcome page click “Next”

Accept the licence and click “Next”

Again note that only DomainPrep will be carried out and that you can change the file location if you want (Only change it if you
changed the location for ForestPrep too)

Click “Next”
Early in the process you will likely be warned that your domain is insecure for mail-enabled groups with hidden DL membership.
Anyone in the Pre-Windows 2000 Compatible Access group can view this membership. So long as you are not using the group for
a valid reason remove the default membership of Authenticated users to remove the problem.

Click "OK"

The DomainPrep is quick and shows the screen below whilst running

Once complete click Finish

Move back to the deployment tools and check the box of the 7th step.

You are now ready to install Exchange.

Move onto step 8. Again enter the path to the install files and click “Run Setup Now”

On the welcome page click “Next”

Accept the licence and click “Next”

This time check the install options carefully. You can choose which components to install. Generally the defaults are fine and that is
what we shall stick with. Note also, that you can change the file location. Again you should do this if you changed the location for
forest and domain prep.

Once you are happy with your selections, click “Next”

As there is no Exchange org setup currently select to create one and click “Next”
Name the org and click “Next”

Agree to the licence and click “Next”

Verify your choices and click “Next”

The installation will progress

When complete click Finish

Now return to the deployment tools and check the box next to step 8.
 Click “Next” on the deployment tools bottom right hand corner

The next page runs through the steps again for other Exchange servers.
For now we will not install another server so again click “Next” on the deployment tools bottom right hand corner.

Read through the post installation steps. We will cover the important items from here, like SMTP Filtering, Memory optimisation
and Connecting to the Internet later on.

Congratulations you have just installed Exchange!

Now let's move on to setting it up the way we want it!.

Exchange 2003 configuration step by step

Configuring your new Exchange 2003 server for internet email with POPcon for
downloading the email from POP3 mailboxes isn't hard if you just do it step by step as
shown in this configuration sample. In this guide we will step through a sample installation
of Exchange 2003 for a company we will call "Mycompany". Mycompany consequently
owns the internet domain name "mycompany.com".

Actually it only takes these simple steps:

1. Adding your internet domain name to the recipient policies

2. Configuring the SMTP server for inbound email

3. Adding a SMTP Connector for outbound emails

4. Configuring the email addresses of your users

5. Installing and configuring POPcon, Exchange POP3 Connector

6. (Optional) Check out the ChangeSender Exchange Send-as Outlook Add-in

And this is how to configure the Exchange Server to accept email for a domain like
"mycompany.com" and cooperate with POPcon:

First install the Exchange server software from the CD or DVD. You may have to go back
to the "Add/remove Software" utility in the control panel to add NNTP support if you did
not do so during initial setup of your windows installation. Then open the Exchange
System Manager and configure the new Exchange installation.

1. Adding your internet domain name to the recipient policies

Open the Exchange System-Manager. It should look like this:
One of the problems most often encountered when configuring an Exchange 2003 Server
system is the fact that often the internet domain nane you want to receive email for
("mycompany.com") does not match your standard active directory domain name (i.e.
"servername.mycompany.com"). The Exchange 2003 Server component handling
incomming emails - the SMTP server - does not accept emails for other domains than the
ones entered in the "recipient policies", even if you entered the correct email addresses
("user@mycompany.com") in the active directory.

To make Exchange accept email for additional domains like your internet domain you
need to add the domain names to the default recipient policy like this:

On the main tree panel of the exchange system manager expand the tree "Recipients"
and then click on "Recipient Policies". The policies will be shown on the right panel.
Normally only the "Default Policy" will be there:
Open the properties of the "Default Policy" by double-clicking it:
In the Default Policy Properties please choose the tab "E-Mail Addresses". There you will
find a list of domains supported by your exchange server. Usually only your internal active
directory server domain will be listed here:
Like you can see, after installing our Exchange Server from scratch only our AD domain
"Christensen.local" was listed as accepted SMTP address. But emails from the internet
will be comming in addressed to "@mycompany.com" and not Christensen.local!

Choose "New..." here to add another accepted inbound domain. Since emails on the
internet are sent via the SMTP protocol we want to add an "SMTP Address":
Now enter the domain name you want to receive email for. Please add a leading "@" to
the domain name. This is what we entered to support emails addressed to
@mycompany.com:

This is how the Default Policy Properties look like after entering the additional SMTP
domain:
Enable the newly created entry with a check mark next to it:
When you OK the above dialog, Exchange will ask you with the next dialog box if you
want to add the new address to all new users. Usually you do want exactly that to save
some typing later.

Please note: You may need to restart your server to activate the new domain!

2. Configuring the SMTP server for inbound email

Next we will configure the SMTP-Server. This is the part of Exchange that accepts
incomming emails from POPcon. No special settings are needed to work with POPcon but
these are the standard settings in any case:
You will find the settings for the SMTP server under Servers/Protocols/SMTP/Default
SMTP Virtual Server. Open the properties by right-clicking on the Default SMTP Virtual
Server and choosing "Properties":

The settings on tab "General" can normally be left to the defaults.

On the tab "Access" you can find some configuration settings that might interfere with
POPcon.
POPcon only works with a standard SMTP connection WITHOUT authentication, so allow
"Anonymous access" in the "Authentication" dialog:
Choose "Connection" to grant or refuse the right to connect to the SMTP server to
individual or multiple IP Address Ranges. Please ensure the system POPcon runs on
does have the right to connect granted. With this setting ALL systems will have access to
your SMTP server:
Under "Relay..." you can assign the right to relay through your SMTP-Server to some
systems. This might be needed in some configuration and to be sure you should grant the
system POPcon runs on relay rights. All other systems will need to authenticate before
accessing the SMTP server to prevent unauthorized users using your system to relay
spam:

Under the "Messages" tab you can restrict message size and number of messages
accepted for each connection. Please make sure these settings are liberal enough to
allow POPcon to transmit large messages to your server.

Also, on this tab you can choose an internal additional recipient for copies of the non-
delivery reports. These NDRs will be sent back to senders of mails addressed to
recipients unknown in your Exchange Server and they include a copy of the original
message sent. You can use these postmaster copies of the NDRs to manually forward
emails sent to mistyped recipients to the correct users.
Under tab "Delivery" some more configuration settings for outgoing emails can be found:
3. Adding the SMTP Connector for outbound emails
Now we need to add an SMTP-Connector (vs. SMTP Server) to handle outgoing email to
the Internet.

Right-click "Connectors" in the Exchange System Manager and choose "New", "SMTP-
Connector" to start adding the new connector and name it appropriately (like "SMTP-Out"
in our case):
On the "General" tab you can now choose wether Exchange will send outgoing emails
directly to the recipients system ("Use DNS...") or if all emails should be relayes through a
SMTP relay server ("smart host").

The first option, DNS, is more direct but can sometimes cause problems when you use a
dialup internet connection because some recipient systems will not accept emails that are
coming from you ISP's dialup IP range while pretending to come from your real internet
domain. Sending via your ISP's smart host / smtp relay server is the better option in this
case. We chose our ISPs smtp relay server here.
Also, on this tab you need to add the "local bridgehead" server (as shown above)

On the tab "Address Space" we need to add a wildcard address space for SMTP. We
want to allow emails to any domain, so we use the wildcard "*" here:
Side note about the "Cost" entry: If you want to send emails to some domains via a
different route you can create multiple SMTP connectors and set the "Cost" entry of this
wildcard connector to a higher value while setting the cost entry of the special domain
route to a lower cost but with only the special domain allowed on this page. This is
especially useful if you generally want to send via DNS and only route to some systems
that won't accept your email via some relay server.

If your ISP's SMTP server requires authentication (and almost all of them do today) you
can set the username and password on the "Advanced" tab of the SMTP connector.
Select "Outbound Security":
Select "Basic authentication" and chose "Modify" to enter the username and password:
And that's alreay it - Your Exchange is now configured to send email to the internet and
receive an SMTP email feed like it will come from POPcon or a direct internet connection.
All you should do now is configure your users' email addresses in the Active directory.

4. Configuring your user's email addresses in the Active Directory

You can set one or multiple email addresses for each user to receive email at. We will
step through the neccessary actions when creating a new user called John Galt.

First open the active directory and right-click the "Users" item to select "New", "User":
The resulting dialog will allow you to create a new AD user to log into your server and
creates an Exchange mailbox all in one wizard pass:
Next...

Next...
Now the wizard continues into the Exchange Server realm and lets us create a new
exchange mailbox

We just accepted the default alias here. Next...

Ok, fine - but wait: What about our desired email address? john@servolutions.com? We
need to add this mail address manually. We are back at the AD configuration console and
select the properties of our new user "John Galt" by right-clicking on the name:

Lot's of tabs on this resulting dialog:

We go to the "E-mail Addresses" tab:
And surprise: john@servolutions.com is already there, but in suspiciously non-bold print.
Actually, Exchange automatically entered this additional email address because we
choose so during the editing of the default recipient policies. But we want this address to
be the primary address meaning all email sent by John will get this address as the
"senders" and "reply" addresses in the mail headers. So we click on "Set As Primary" and
are done:
We could also add more email addresses like info@servolutions.com or
sales@servolutions.com but only one of these addresses can be the primary address that
will be the default senders' address in all emails sent out by john.

And that's really it - just step through you other user's AD entries and set the appropriate
primary and additional email addresses.

5. Installing and configuring POPcon or POPcon PRO

After going through the above 4 steps your Exchange is configured to send out email but it
still can't pull down email from POP3 or IMAP mailboxes on your provider server. For this
you need to install and configure POPcon.

Configuring POPcon is quite straightforward. You need to follow these steps:

a) Configure a Postmaster email address on the GENERAL configuration tab.

b) Add one or more POP3 mailboxes on the POP3/IMAP tab.

c) Configure the Exchange server name on the EXCHANGE configuration tab.

Download and run the self-extracting installer of POPcon or POPcon PROand follow the
instructions during the installation. It will install the POPcon Administrator program and the
POPcon service that runs in the background on your system.

Run POPcon Adminstrator from Start > Programs > POPcon

POPcon Screenshot

Click on "Configure" to open up the POPcon configuration screen.

a) Configure a Postmaster email address on the GENERAL configuration tab.

On this first configuration page you only need to enter the email address of your
Postmaster or Administrator user. The Postmaster will receive all emails without a valid
recipient as well as general POPcon status notifications. It is very important to define a
real email address from inside your exchange server here because mails can be lost
irretrievably if POPcon forwards some mail with no recipient information to the postmaster
and that account does not exist in your exchange server.

You can leave the log file options to their default settings for now.

Next go to the POP3/IMAP tab to configure the POP3 or IMAP mailbox accoutns you want
POPcon to download email from.
b) Add one or more POP3 mailboxes on the POP3/IMAP tab.

POPcon PRO collects mail from as many POP3 accounts you like. Just click on Add to
add another POP3 host or account to the list of Polled POP3 Hosts. For each server or
account you need to fill in the POP3 server settings as shown below.

If you are using catch-all style mailboxes (mailboxes that receive email for a whole
domain, regardless of the recipient part before the "@") POPcon needs to filter recipients
from incoming mail so only the recipients at your own internet domain are accepted.
Please add the domain you consider your own in the "Accepted Recipient Domains" box.
This is the same domain you configured earlier in the Exchange Default Policy.
Individual account settings

This dialog lets you input the specifics about a POP3 or an IMAP server you want to have
polled by POPcon PRO.

This is the information POPcon PRO needs to know about each server:

Server type:
Here you can select on the four supported server types:

POP3: Default. POP3 servers are by far the most common mail server types on the
internet.

POP3-SSL: Some POP3 Servers need SSL encryption enabled for the connection in
order to protect passwords and sensitive information. Choose this type to have a SSL-
encrypted connection to a POP3 server.

IMAP: IMAP Servers are also quite common and theoretically allow the client to
manipulate email folders and move email between folders online. In our case the protocol
is used to download email from the INBOX of the IMAP server to your exchange server.

IMAP-SSL: Supports SSL connections to IMAP servers for added protection.

Access:
Configure the server name, account name and password to connect to the mail server
here.

Servername: The name the server you want to have polled. You can also enter the IP
address directly.

Username: The username needed to log into your POP3 or IMAP mail server.

Password: The password needed to log into your mail server.

IP portnumber: Almost always the TCP/IP port for POP3 mail is 110. Under some
circumstances, internet routers or firewalls change the port number. Please ask your
network administrator or internet provider. The standard port for POP3-SSL is 995, for
IMAP it is 143 and for IMAP-SSL this should be set to 993.

Timeout: Leave this to the default value.

Please ask your POP3 mailbox hosting provider if you do not have the above information.

Type of mailbox / distribution:

POPcon PRO supports both catch-all and single user mailboxes

Catch-all mailbox ("*@domainname.com"): For this type of mailbox, POPcon PRO will
distribute the email retrieved from this server according to what it finds in the TO:, CC:,
BCC: and other header-fields of the mail. If you choose this option, don’t forget to add
your internet domain name(s) to the "Accepted Recipient Domains" box. on the
POP3/IMAP configuration dialog

Single user mailbox ("user@domainname.com"):This type of mailbox receives email

for only one specific Exchange mailbox. You need to specify the receiver of the email
here. POPcon PRO will then direct all mail retrieved from this server to the recipient email
address given here.

Delete / keep email on the server:

This block allows you to configure POPcon PRO to either delete email after downloading
or keep it on your POP3 or IMAP server for a specified amount of time or indefinitely.

Delete downloaded email: This is the default setting – POPcon PRO will delete the
Email on your POP3 or IMAP server after successfully downloading it.

Leave a copy of downloaded email (indefinitely):This option will cause POPcon PRO
to leave a copy of the email on the server. Only use this option during testing or when you
are sure the mail will be deleted eventually, i.e. by another system periodically
downloading an deleting email.

Leave a copy of downloaded email for n number of days: Causes POPcon PRO to
leave a copy of the email on the POP3/IMAP server for the specified number of days
before deleting it. You can use this option to allow access to a single POP3 or IMAP
mailbox by two different systems.
c) Configure the Exchange server name on the EXCHANGE configuration tab.

On this configuration screen you can specify the Exchange™-(SMTP) Server you want the
mail to be directed to. Normally this will be the computer name of your Exchange™ server
(like "MYSERVER").

You can leave all other settings default

These three steps to configure POPcon will provide you with a working set-up. Test it out
by confirming the new configuration with OK and then use the "Trigger mail retrieval"
button on the POPcon Administrator main screen to start the first mail download. You can
follow what is happening in the scrolling log display on that screen. Watch out for any error
messages there. There is also a POPcon log file (c:\program files\POPcon\POPconSrv.log
– open with notepad) that you can view at your leisure.
6. Check out the ChangeSender Outlook Add-in
ChangeSender Exchange Send-as Add-in adds one important piece of functionality to
Microsoft Outlook when used with Exchange Server: It allows you to send as any of your
email addresses and even group addresses or those of other users if allowed by the
administrator. Effectively this is the Exchange Send-as function without the limitations of
the ActiveDirectory

Without the ChangeSender Exchange send-as components, Exchange always sends

out emails on your default email address fixed in the ActiveDirectory even when
answering emails received on one of your additional email addresses. Also, Exchange
does not allow sharing the same email address (i.e. department-wide or company-wide
email addresses) between users. ChangeSender solves both problems by adding a
configurable "send as" selection box to your Outlook email form.

ChangeSender Features

Automatically selects the right send-as address when replying to

emails. ChangeSender uses the address of the original email as sender address for
replies.

Easy selection of send as addresses for new emails via a new sender address selection
box in Outlook.

Multiple users can send from the same sender address (i.e. send as
sales@yourcompany.com or support@yourcompany.com)

Sender appearance fully configurable as "Any name" <any@address.com> for each

individual email address. Does notshow up as "sent on behalf of...".

Very simple installation and administration.

Administrator can restrict or allow user choices for the sender address and prevent users
from sending as other users.

Works with Exchange 2010, 2007, 2003, 2000 and with Outlook 2010, 2007, 2003, 2002,
2000 versions.
ChangeSender in Outlook 2007 screenshot

Exchange Server 2003/2000- Inbound

STEP C1: Start Exchange System Manager.

From your Windows Start Menu, select:Start Programs > Microsoft Exchange > System Manager

STEP C2: Setting Default SMTP Recipient.

In Exchange Server you will have to give all the clients SMTP type addresses which match their Internet email
addresses. For example say a user is known as john@acme.com on the Internet, then the Internet address is
john@acme.com for the Exchange Client.

To make sure the Virtual SMTP Server accepts messages for your domain you must modify the default SMTP
address. To do so follow these steps.In the Microsoft Exchange Systems Manager select: Recipients >
Recipient Policies
In the details pane, using your mouse's RIGHT BUTTON right -click Default Policy and then click Properties.
Exchange Server 2003/2000- Inbound

Click the E-Mail Addresses tab.

Under Generation rules, select SMTP, and then click Edit. The SMTP Address Properties dialog will appear. In

Address, type the new default SMTP recipient address that is in the form: @yourdomain. Click OK to exit the SMTP

Address Properties dialog and then Click OK to exit the Default Policy

Properties dialog.

Exchange Server 2003/2000- Inbound

From Microsoft Exchange Service Manager select:

Servers > your exchange server > Protocols > SMTP > Default SMTP Virtual Server

Using your mouse's RIGHT BUTTON right-click Default SMTP Virtual Server. Then select Properties from the
popup menu.
Exchange Server 2003/2000- Inbound
Make note of the IP address shown in the IP Address field. The value will either be an IP address (example:
192.168.0.4) or be 'All Unassigned'. You will need to know this value later when configuring eXchange POP3.

Click OK.
Exchange Server 2003/2000- Inbound

STEP 6: Configure eXchange POP3.

Now run eXchange POP3 and select:

eXchange POP3 > Configuration > Exchange Connection

IP Address or TCP/IP Host Name: Enter the IP address you noted in Step C.5. If the value was 'All Unassigned'
then enter the host name or IP address of the computer running Exchange Server.

Exchange's SMTP server listens on port: Enter 25.

Click the Save button on the toolbar.

Now eXchange POP3 is configured to send any mail it downloads to your Exchange Server. Exchange Server is also
now configured to receive mail from eXchange POP3.
Exchange Server 2003/2000- Outbound 32
OPTIONAL
The following steps deal with configuring Exchange Server and eXchange POP3 so that Exchange Server can send
its Internet-bound messages to the Internet through eXchange POP3.

STEP D1: Start Exchange System Manager.

From your Windows > Start Menu, select: Start Programs > Microsoft Exchange > System Manager
From Microsoft Exchange Service Manager select:

Servers > your exchange server > Protocols > SMTP > Default SMTP Virtual Server

Using your mouse's RIGHT BUTTON right-click Default SMTP Virtual Server. Then select Properties from the
popup menu.
Exchange Server 2003/2000- Outbound 33
Click the Delivery tab.

Click the Outbound Connections button.

Exchange Server 2003/2000- Outbound 34
Set the port number that eXchange POP3 will be listening on for email connections fromExchange Server.

Exchange Server and eXchange POP3 running on SAME computer: Set the TCP Port to 8025 as not to conflict
with port 25, which is typically used by ExchangeServer.

Exchange Server and eXchange POP3 running on DIFFERENT computers: Set the TCP Port to 25
(default).

Click OK.
Exchange Server 2003/2000- Outbound 35
At this point you should be back to the Delivery property page. Click the Advanced button on this page.
The dialog determines where Exchange Server sends it Internet messages.

In the Smart Host field enter the host name or IP address of the computer where eXchange POP3 is running. NOTE:
If you enter an IP address you must enclose it in square brackets []. For example if

the IP address is 192.168.0.4 then enter [192.168.0.4]. Click OK.Click OK to save your changes and exit the Default

SMTP Virtual Server Properties dialog.

Exchange Server 2003/2000- Outbound 36
STEP D6: Configure eXchange POP3.

Run eXchange POP3 and select:

eXchange POP3 > Configuration Exchange Connection

Exchange Server sends to Internet....

Enable this checkbox.

Listen for Exchange SMTP....

If eXchange POP3 and Exchange Server are running on the same computer enter 8025. If eXchange POP3 and

Exchange Server are running on different computers enter 25. Click the Save button on the toolbar.