• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Exchange 2003(SBS2003) and public domain problem

Here is the scenario:

SBS 2003 and the internal domain is MyDomainServer.Local and the public domain is MyDomain.com.  There are 10 users all of which have domain accounts with the corresponding SMTP addresses…user@MyDomainServer.Local and users@MyDomain.com.  Only 5 of these users actually log on to the SBS domain and Outlook setup for Exchange the other half are peer to peer and get their email from the ISP (POP3) which is still hosting the mail server (MX record) for MyDomain.com.  The Exchange users are setup to have their POP3 mail pulled from the ISP (same username) via the POP3 Connector and delivered to their Exchange mailbox.  A Smart Host (the ISP’s SMTP server) is configured on the “SmallBusinessSMTPConnector” to deliver mail to the outside world when sent from the Exchange clients.

When a user who is on the domain, user1@MyDomain.com sends mail to a user not on the domain, user2@MyDomain.com, user2 does not get the message (in ISP POP3 mailbox) because it never leaves the SBS server and is delivered to the Exchange Mailbox.  Furthermore there are some email accounts hosted at the ISP, others@MyDomain.com, that are not associated to any user accounts on the SBS server and when mail is sent from inside the domain they are not delivered but a system admin error is returned.  (I forget the exact message)

Diagram

MyDomain.com – ISP                           MyDomain.com – SBS2003
User1@MyDomain.com      <- User1@MyDomain.com (delivered to Exch Account)
User2@MyDomain.com      <- User2@MyDomain.com (delivered to Exch Account)
Other Accounts at ISP only
User3@MyDomain.com (will not sent out from SBS2003 - error)   <- User1@MyDomain.com
User4@MyDomain.com (will not sent out from SBS2003 - error)   <- User2@MyDomain.com

The client wants to have some users not on the Domain.  They do not want to let the Exchange server be the mail server for MyDomain.com.

From what I can tell from my research is that this is Exchange behavior is by design.  It believes that it is the only MyDomain.com there is and would have to be tricked into making this scenario work.

What I am looking for is “Best Practice” not a hack or a trick.

Experts only please advise.

Thanks,

John
0
JohnHockett
Asked:
JohnHockett
  • 3
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You just need to add an entry to the Exchange configuration to allow messages for those who do not have Exchange mailboxes to be redirected to your ISP's mailserver.

In your Server Management Console, navigate to:
Advanced Management > First Organization (Exchange) > Servers > Servername > Protocols > SMTP > Default SMTP Virtual Server.  Right click that and select Properties.

Then select the MESSAGES TAB and at the very bottom you'll see "Forward all mail with unresolved recipients to host"
In this box enter the FQDN of your ISP's mail server (ie, mail.domain.com).  There's a good little overview about how this works if you click help on that particular window.

That's all there is to it... :-)

Jeff
TechSoEasy


0
 
JohnHockettAuthor Commented:
Jeff,
I can see how this would work for the addresses @MyDomain.com that are not on the Exchange Server, but what about those users who have accounts on the Server but are not accessing the server for those messages.  Maybe, only users that are logging onto the SBS server get mailboxes and users who do not are removed.  Then when a message is sent to User3@MyDomain.com (no domain account) it would be handled by the entry here ... "Forward all mail with unresolved recipients to host" and sent to the ISP for resolution as you suggest.

I will give this a try.

John
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
The issue is whether or not you have a CAL for the user.  If you do, and you've created an account on the server for them along with a mailbox, then why don't they get their email from the Exchange Server?  (via OWA?).

For that matter, how many users do you have?  You really should consider having Exchange handle your email rather than your ISP since it's more secure that way and you have more control over it.  Plus, the POP3 connector is really only there to provide a transition for you to get to Exchange anyhow.

More info about how to do this is here:  http://sbsurl.com/pop2smtp

Otherwise, what you have described above is correct... if they aren't logging onto the SBS, then why would you have a mailbox for them?

Jeff
TechSoEasy
0
 
JohnHockettAuthor Commented:
TechSoEasy,

Thanks for the help. The client did this and they are happy with this solution.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Another day, another satisfied customer.

Jeff
TechSoEasy
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now