Have installed Exchange on SPS 2003 but users are still connecting to their POP3 accounts at ISP. I have created a mailbox for myself on Exchange using the POP3 connector to download my mail from ISP. We have two email domains at ISP, and I am now able to send and receive internet email, but cannot send or receive email to users in the two registered email domains.
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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Exchange problem 2
- Thread starter maya14
- Start date
- Thread starter
- #2
Maybe I must provide more details:
This is a new setup of SBS.
Exchange on SBS has .local domain with 192.168.0. IP.
We have one ISP for the POP acounts and other for ADSL internet and DNS.
We have domain A and domain B at POP ISP.
I have only added my mailbox to the POP Connector Manager in Exchange for testing purposes.
I cannot understand why I can only send and receive normal internet mail but cannot receive or send email from users @ domain A and B.
When I ran the Internet and email wizard I specified both IP;s for the 2 domains.
Perhaps missing or incorrect DNS records??
This is a new setup of SBS.
Exchange on SBS has .local domain with 192.168.0. IP.
We have one ISP for the POP acounts and other for ADSL internet and DNS.
We have domain A and domain B at POP ISP.
I have only added my mailbox to the POP Connector Manager in Exchange for testing purposes.
I cannot understand why I can only send and receive normal internet mail but cannot receive or send email from users @ domain A and B.
When I ran the Internet and email wizard I specified both IP;s for the 2 domains.
Perhaps missing or incorrect DNS records??
-
1
- #3
Because Exchange is authoritative for those domains (assuming they appear in your recipient policies). That being the case, email sent to someone @domain A or @domain B won't go out through POP3. And shouldn't.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
-
1
- #4
For your exchange server to receive email from the internet, you need to change your MX records for the public domains to point to your public IP address. That way, when someone sends an email to you@yourdomain.com it will bypass your ISPs POP server and go to your exchange server.
The internal IP of your SBS server is only needed for your firewall to forward the smtp email to your sever. so you must make sure that your firewall or internet gateway device is setup to relay email to your exchange server.
Hope that helps you out some.
PS. once you get email flowing correctly, you will have to reconnect all your clients to your exchange server.
The internal IP of your SBS server is only needed for your firewall to forward the smtp email to your sever. so you must make sure that your firewall or internet gateway device is setup to relay email to your exchange server.
Hope that helps you out some.
PS. once you get email flowing correctly, you will have to reconnect all your clients to your exchange server.
That's getting too far ahead. First, you have to mailbox enable the users. Then, you'll see that when you send mail to those users, it ends up in their Exchange mailboxes.
As I stated above, mail for your internal domain won't go out over POP3. That's intelligent design.
Mailbox enable them, then add the Exchange accounts to their Outlook. After that, it's all seamless.
Verify the reverse DNS entry is correct.
Change the MX records to point to your public IP
Remove the POP3 settings in Outlook
kill the POP3 mailboxes and any related connectors
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
As I stated above, mail for your internal domain won't go out over POP3. That's intelligent design.
Mailbox enable them, then add the Exchange accounts to their Outlook. After that, it's all seamless.
Verify the reverse DNS entry is correct.
Change the MX records to point to your public IP
Remove the POP3 settings in Outlook
kill the POP3 mailboxes and any related connectors
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Thread starter
- #6
Must any of the ISP's create any DNS records for Exchange to work as our ISP that hosts the POP3 accounts do not give DNS support to clients?
How do I verify that the reverse DNS entry is correct?
To test my scenario, I have added a second user on Exchange and I am now able to email that user which belongs to one of our other domains and it seems to work without changing any DNS records.
So it seems to me that I will have a problem migrating 40 users that access their POP account directly to Exchange as in the interim those on Exhcnage wont be able to email those still getting their mail from the POP account.
How do I verify that the reverse DNS entry is correct?
To test my scenario, I have added a second user on Exchange and I am now able to email that user which belongs to one of our other domains and it seems to work without changing any DNS records.
So it seems to me that I will have a problem migrating 40 users that access their POP account directly to Exchange as in the interim those on Exhcnage wont be able to email those still getting their mail from the POP account.
Well, they don't HAVE to. But they'd lose customers real quick.
For the rdns record, go to and check your public IP address.
Migrating 40 people isn't hard at all. You can create a Maintenance package using the Office Resource kit, and push it out with a GPO. That will configure Outlook automatically.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
For the rdns record, go to and check your public IP address.
Migrating 40 people isn't hard at all. You can create a Maintenance package using the Office Resource kit, and push it out with a GPO. That will configure Outlook automatically.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Thread starter
- #8
Perhaps i'm just too inexperienced in Exch 2003 and my director is getting very impatient.
I have setup no DNS records when configuring Exch on SBS.
All i know is that once users have Exch mailboxes i can download their email from POP account and deliver it to Exch mailbox and we can send email to each other.
But i still dont understand why cant we send email to the rest which is still using POP to Outlook without Exch.
Must i create i MX on SBS that points to our public IP on router.
We have .local domain on SBS and 2 registered email domains at ISP.
I have setup no DNS records when configuring Exch on SBS.
All i know is that once users have Exch mailboxes i can download their email from POP account and deliver it to Exch mailbox and we can send email to each other.
But i still dont understand why cant we send email to the rest which is still using POP to Outlook without Exch.
Must i create i MX on SBS that points to our public IP on router.
We have .local domain on SBS and 2 registered email domains at ISP.
maya14 said:
Because when you attempt to send mail, Exchange grabs and realizes you haven't configured those accounts in Exchange. It's as simple as that.
As far as your MX records, no - you don't create that internally unless you're hosting your public DNS.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Yep. MS doesn't want you to use it, either. That's why the POP3 connector only supports intervals as low as 15 minutes.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Thread starter
- #12
Thanks for all the advise but where does it leave me now?
We have Exchange and i must get it to work with the POP connector until such time that i can get an ISP to forward all our mail their server for mail relay to the Internet.
58Sniper said that i do not create any MX records internally... I thought i must create DNS records on the SBS to point to our email domains to point to our public IP address on router.???????
We have Exchange and i must get it to work with the POP connector until such time that i can get an ISP to forward all our mail their server for mail relay to the Internet.
58Sniper said that i do not create any MX records internally... I thought i must create DNS records on the SBS to point to our email domains to point to our public IP address on router.???????
Your internal DNS records have nothing to do with the DNS of the internet. Your server has no authority to make the changes. You have to have your ISP and your domain registrar create the necessary records so that your mail server name resolves to your WAN IP address.
- Thread starter
- #14
I have in the meanwhile discussed this issue with our ISP that hosts our POP email accounts and they dont give support to Exchange clients nor do they create DNS MX etc. They are only there for clients with no internal mail servers.
But yet i have setup a mailbox on Exchange for myself and i can send and receive email to the anyone except those belonging to our 2 email domains at ISP. I assume that they must first have local Exch mailboxes for this to work.
How do this email delivery work if i or the ISP have not created any DNS records for our newly setup Exchange server.
But yet i have setup a mailbox on Exchange for myself and i can send and receive email to the anyone except those belonging to our 2 email domains at ISP. I assume that they must first have local Exch mailboxes for this to work.
How do this email delivery work if i or the ISP have not created any DNS records for our newly setup Exchange server.
Your MX records need to be created at the public DNS authority for your domain name. With many/most companies, that's with the ISP. But it may be the domain name registrar. YMMV.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Status
Similar threads
- Locked
- Question