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

Exchange Server for Internal Mail Only, Pop for External


I have 2 clients who have Exchange 2000 Servers that they want to use for internal functions and internal email only.  They have an external pop server through their websites that they want to download mail from and have process their outgoing internet mail.  But they want their Exchange server to process email for internal email addresses and they want to store any downloaded mail in their Exchange mailboxes.

So, I set them up with Outlook XP and Outlook 2003.  They have accounts setup on Exchange and their external email accounts, with the external accounts set as default.  

One of them has a continuous problem of emails being bounced by their Exchange Server saying it could not be delivered.  These email addresses are external and should not be going to the Exchange server.  They also have the problem that when emails do go to internet email addresses, the people who reply to those messages get an error because the reply address is username@servername.local

I would much appreciate help on this.
  • 2
1 Solution

I suggest you change the layout of your system a bit: Use the external domain name inside your AD organisation and use Exchange for both internal and external email by using a POP3 connector software. This will result in a much cleaner setup without the side-effects you described (wrong email addresses, bounces, etc.)
These are the steps:

1.      Configure Exchange to accept emails for yourcompanydomain.com instead of only servername.local:
You can add an external domain name to your Exchange/AD and use that in addition to the servername.local name for email addresses or even exclusively and get rid of the servername.local email addresses.
- Open the Exchange System Manager, Recipients>Recipient Policies>Default Policies>Properties
- Go to the Email Addresses tab and click on New
- Choose “SMTP Address” and enter your external domain (“@yourcompany.com”)
- Activate the new domain with the checkmark left to it in the list.

This allows your Exchange Server to accept email for addresses @yourcompany.com. Exchange will no longer send out email for this domain to the internet. Instead, Exchange will handle all email to this domain internally.

2.      Add the external email addresses to the users’ AD configuration and set those as default addresses – you will already have done that.

3.      Set up a POP3 connector software to download the emails and forward them directly to your Exchange server instead of pulling down email on the clients. If you use the SBS version of Exchange you can use the internal POP3 connector or you can use a commercial one like POPcon (http://www.christensen-software.com/popcon.htm).

4.      If you did not do this before  (not entirely clear by your description) setup an Exchange SMTP Connector for the outbound email and route that through your ISPs SMTP server as a smarthost. See http://www.christensen-software.com/support/installexchg2000.htm for more information on how to do this.

- Claus
hydraziAuthor Commented:
I have decided to try your solution a bit at a time.  First I configured the Exchange server with an SMTP Virtual Server then an SMTP connector as outlined at  http://www.christensen-software.com/support/installexchg2000.htm

I added the full email address that we want for each person and made it the primary.  Email does not want to flow out of that server, it seems.  It does not want to leave the server.  It tries to go through the connector but then says the domains are unreachable.

Can you post the exact error message?
Out of the blue I would guess it is either a problem with your ISP's SMTP relay server which you entered as smarthost in the smtp connector (most probably it needs authentication - you can set that via the "outgoing security" button on the advanced tab) or it's the other domains not accepting your email because exchange is configured to send it out "via DNS" without an SMTP relay server and the destination servers don't like your reverse-DNS name.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

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