Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange setup

Status
Not open for further replies.

maya14

Technical User
May 8, 2007
274
ZA
I have been investigating my problem for some time now but is still clueless about the following:

Our current ISP give no support to Exchange DNS records but only do POP3 accounts.Will be moving to new ISP soon. I have however gone ahead and configure Exchange to the best of my knowledge considering the following:
We have 2 registered email domains. Domain A and B.
I have tested Exchange by creating a mailbox for myself and configuring the POP connector.
I can send email everywhere but not to people @domain A or B.I have to use my external POP3 server for that to work. Only if create a mailbox on Exchange i can send email to the user.
My problem is that not all users in domain A or B can connect to our Exchange server so how do i solve this email delivery problem.
 
You should have everyone connect to that server. By adding a domain to Exchange, it thinks it's authoritative for that domain. If it doesn't have a record of an email address, it believes it doesn't exist, and bounces it.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
 
Thats what I thought, but unfortunately I cannot add everyone on domain A or domain B to the Exchange server and yes both domains have been added in Exchange.
How can I fix this problem having half on Exchange and other half on POP3 with ISP but all belonging to @emaildomainA . Or any other ideas how to solve my problem???
 
Not without creating the potential for a mail loop. Why can't you add them all to your Exchange server?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
 
Some users cant be part of the domain due to the following:
1. Geographical locations
2. Lack of network infrastructure on their side.
3. Financial implications
I know users can use OWA but we dont have static public IP for our Exchange. We use DynDNS to sort that out.
Also remote users not belonging to the domain want to use Outlook a web interface.

At our HO we have users belonging to 3 different email domains. All using POP with ISP, but it's expected of me to implement Exchange at HO level.


So what do you guys suggest i do with this scenario.
 
Also remote users not belonging to the domain want to use Outlook NOT a web interface.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top