Configure for multi. domains, relay, and smarthost (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Server Security



Message

douglas168 -> Configure for multi. domains, relay, and smarthost (4.Jun.2008 1:04:24 PM)

Hi, I need to confiure our Exchange 2003 for multiple domain use, relay use, and outbound smarthost but I have the following questions.  Hope someone can answer them for me.

1- I know you use Recipient Policy to add more email domains.  If you check off all the domains, would it create all those email addreses (i.e. use1@domain1.com user1@domain2.com) for all the users automatically?  If so, does it mean I have to create one RP for each domain?

2- To allow relay, you configure SMTP Virtual Server.  What is difference between 'Connection' and 'Relay'?  I should add all IP range where connection is allowed and add internal IP of servers that require relaying, right?  In regard to multiple domains, email from one domain to another on the same Exchange server is consider connection or relaying?

3- What is the difference between configure smarthost on SMTP connector vs. on SMTP Virtual Server?   If I am doing multiple domains, where should I configure it?

Appreciate the help,
Douglas



Sembee -> RE: Configure for multi. domains, relay, and smarthost (4.Jun.2008 5:17:34 PM)

The best practise is to leave the default recipient policy alone and create additional polices. If you want different users to get different email addresses then you would create a separate recipient policy for each user.

For relay settings - you normally do not touch those. Relay means exactly that - what addresses can be relay through the server. Connection means what servers can connect to the server. If the server is going to be exposed to the internet then usually you do not want any servers set to relay and you do not want any servers restricted from connecting - otherwise you will not receive email.

Smart hosting on the SMTP virtual server is against best practise and should not be used. If you set a smart host on the SMTP virtual server then all email, whether it is destined for, will go to that smart host. You cannot control where the email goes. If you introduce a second server then a smart host on the SMTP VS will cause a problem. Always use an SMTP connector. You can have more than one SMTP connector allowing you to route email in different directions.

As the server is hosting multiple domains, the recommendation I make is to use the same DNS information for all domains. Exchange doesn't route email based on the sender, only the recipient. Therefore to ensure that your DNS passes antispam tests, use the same information. MX records do not have to be in the same domain that they are for - so mail.domain.com can be the MX record for domain.net

Simon.



Gigabitz -> RE: Configure for multi. domains, relay, and smarthost (4.Aug.2008 1:39:50 PM)

So if it's against best practice is the below information incorrect.  I inherited a domain with numerous smart host devices and I am debating whether to use IIS or Exchange virtual SMTP servers to act as smart hosts.......any guidance

How to Configure Exchange Server 2003 to Use a Smart Host IP Address
View products that this article applies to.function loadTOCNode(){}





Article ID
:
821911

Last Review
:
December 3, 2007

Revision
:
2.4
For a Microsoft Exchange 2000 Server version of this article, see 257426 (http://support.microsoft.com/kb/257426/).
SUMMARY
loadTOCNode(1, 'summary');

This article describes how to configure Exchange Server 2003 to use a smart host IP address. MORE INFORMATION
loadTOCNode(1, 'moreinformation');

You can route all outgoing messages for remote domains through a smart host instead of sending these messages directly to the domain. When you do so, you can route messages over a connection that may be more direct or less costly than other routes.

Note The smart host setting for SMTP virtual servers is similar to the smart host setting on SMTP connectors. You can configure multiple smart hosts on the connector, because connectors can handle message delivery on a per-domain basis.

You can identify the smart host by either a fully qualified domain name (FQDN) or an IP address.

Note If you change the IP address, you must change it on every virtual server. If you use an IP address, you must enclose it in brackets ([]). Exchange Server 2003 checks first for a server name and then for an IP address. The brackets identify the value as an IP address. As a result, the DNS lookup is bypassed.

You can specify multiple smart hosts based on either the FQDN or the IP address. If you specify multiple smart hosts, you must separate them by a semicolon (;). If you use a combination of IP address and FQDN, make sure that the smart hosts that are specified by IP address appear after those that are specified by the FQDN. For example, you can use the following combinations:



•
IP address of smarthost1; IP address of smarthost2

•
FQDN of smarthost1; FQDN of smarthost2

•
FQDN of smarthost1; IP address of smarthost2The following combination does not load balance:



•
IP address of smarthost1; FQDN of smarthost2Microsoft recommends that you configure smart hosts on the connector because connectors can handle message delivery on a per-domain basis.

To configure Exchange Server 2003 to use a smart host IP address, follow these steps:



1.
Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

2.
Locate the following folder:
Servers/Your_Server/Protocols/SMTP/Your_SMTP_Virtual_Server

3.
Right-click Your_SMTP_Virtual_Server, and then click Properties.

4.
Click the Delivery tab, and then click Advanced.

5.
In the Smart host box, type the name of the smart host server.

You can type a string to represent a name or type an IP address that is enclosed in brackets.



Sembee -> RE: Configure for multi. domains, relay, and smarthost (4.Aug.2008 2:11:10 PM)

Yes - I am aware that Microsoft have that article on their web site.
It also doesn't help that some outsourced vendors recommend that method as well.
If you have multiple servers then a smart host on the SMTP virtual server is a bad idea. It overrides whatever the Exchange server finds. Therefore if you have multiple smart hosts on SMTP connectors AND a smart host on the SMTP virtual server then the smart host on the SMTP connectors are not being used.

As far as I am concerned, there are no debates. Use SMTP Connectors.
While you can have multiple SMTP virtual servers you cannot control which one Exchange will use. Therefore if you want to send email to different smart hosts then you must SMTP connectors.

Simon.



Gigabitz -> RE: Configure for multi. domains, relay, and smarthost (4.Aug.2008 3:21:43 PM)

I thought the smart host settings on the connectors over ride those on the VS?  I have 4 different Smart Hosts for 16 Exchange 2003 Enterprise servers.  I want to use either IIS as a smart host or configure something in exchange so I can get rid of the 4 smart hosts which are really good servers that I can use for other applications.  What do you suggest for my situation?



Sembee -> RE: Configure for multi. domains, relay, and smarthost (4.Aug.2008 7:02:09 PM)

Basically it becomes a mess when you put smart hosts on the SMTP virtual server, so it is best not to do it at all. If you must use smart hosts put them on SMTP Connectors.

Do you need smart hosts at all? Can you not send email via DNS directly from each server? Or have them all send email to a single host for sending outbound? That can all be done with SMTP connectors.

If you have multiple servers then I am surprised that you haven't had problems if you have smart hosts on the SMTP virtual server with inter-server delivery.

Simon.



Page: [1]