Administration Guide
Simply Transport Agent for Exchange 2010/2013. Extend Exchange mail routing based on sender domain or Group.
How to configure Global Routing Table
1. Run “SimplyManagementTool.msc”
2. Verify you create SendConnector using proper Address Space, this address space is not target domain you will send to. This address spaces is next hop.
3. Create Routing Table to set specific domain sending to designated “SendConnectoer”
a. Click “Global Routing Table” on left pane
b. Click “New Routing” on Actions pane
3. Type routing info
a. Routing Name: Routing name
b. Sender Domain: “prov.com”
c. Recipient Domain: “*” is all domai (If you want to scope specific domain, type domain name)
d. Next Hop: Next Hop in sender connector as address space
4. Review Routing Table you created
How to configure Routing Group per server
Create Server Routing table. Server Routing table is belong to each server. This routing table is only applied to server. This server routing table is based on Active directory group. Any user sending from in designated group will be applied. This server routing table take have the precedence of over global routing table
1. Click “Server Routing Table” on left pane and choose proper server name.
2. Click “New Group” in Actions pane.
a. Group Name: Group name
b. Priority: 0 is highest, bigger is lower priority.
c. Choose Active Directory Group by clicking button “…”
d. Recipient Domain: * is all recipients.
e. Next Hop: Next Hop in sender connector as address space.
How to create a Rewrite Entry
This rewrite entry table is to change sender address; you can archive this same task by creating rewrite entry on Exchange Edge server.
However you should create same rewrite entry table in each all edge server.
This feature of Simply Exchange Transport Agent is able to simplify and manage rewriting sender address at central management tool.
Routing Scenario Example
1. SendConnector lists
| Name | Address Space | Smart Hosts |
|---|---|---|
| ArchivingSendConnector | to.archiving.com | 10.10.0.1 |
| ReviewSendConnector | to.review.com | 10.10.0.1 |
| EncryptionSendConnector | to.encrypt.com | 10.10.0.1 |
2. Global Routing
| Type | Name | Sender Domain | Recipient Domain |
|---|---|---|---|
| Global Routing | GR1 | igoodworks.com | * |
| Global Routing | GR2 | igoodworks.com | yahoo.com |
Simulation
• Send to james@hostmail.com from test1@prov.com
• Result: Next hop is “to.archiving.com” by RE1 and GR1
• Send to peter@yahoo.com from test1@prov.com
• Result: Next hop is “to.review.com” by RE1 and GR2
3. Routing Group
| Type | Name | Active Directory Group | Recipient Domain | Next Hop |
|---|---|---|---|---|
| Routing Group | RG1 | LegalDL | google.com | to.encrypt.com |
• sales@igoodworks.com is a member of LegalDL
• Send to peter@google.com from sales@prov.com
• Result: Next hop is “to.encrypt.com” by RE1 and RG1
4. Rewrite Entry
| Type | Name | Domain | Email Address | New Address |
|---|---|---|---|---|
| Rewrite Entry | RE1 | prov.com | * | igoodworks.com |
| Rewrite Entry | RE2 | prov.com | * | david@prov.com |
• Send to peter@google.com from david@prov.com
• Result: Next hop is “to.encrypt.com” by RE2 and RG1
