I'm sorry it has taken over a week for someone to respond to your
question, perhaps the reason being that you probably won't be 100%
satisfied with the solution After researching this issue, I've
discovered that you are not alone and what you describe is a common
complaint. For possible solutions, please click on the following links
for full details.
PROBLEMS USING EXCHANGE FOR INTERNAL EMAIL ONLY
"A number of small businesses have a problem with their topology --
they use an Exchange server that is not connected to the Internet and
a separate connection to an ISP for external mail. They use the
Exchange server for internal mail and calendaring, while all external
email is sent via a POP3 account in Outlook to the ISP. The POP3
account is configured as the default, the Exchange account is
Each version of Outlook handles this scenario a bit differently, but
when it worked, it worked fine. When it fails, as it often does, it
causes headaches all around.
In Outlook 2003 when the SMTP transport is presented with an Exchange
address it opens the address book entry for that recipient and uses
their default SMTP address. So now, in the above topology, sending a
message to mixed internal/external recipients sends it to all
recipients via the ISP. Since Exchange is not on the Internet, the
SMTP addresses for internal recipients are not deliverable and all
internal recipients bounce. If you reverse the order of the accounts,
Exchange handles all recipients but bounces all external recipients
because it doesn't have an Internet connection for SMTP."
"The simplest solution is to add the user's external SMTP address to
their Exchange account as the default SMTP. The messages will be
deliverable this way, although you may not want internal messages
going out the Internet. Not only does it increase bandwidth, sending
confidential documents to an Internet account may be a security
A better solution goes one step farther. Not only do you add each
users external SMTP address as their default SMTP, you also configure
Exchange to send mail to the Internet, either directly or by
forwarding it to your ISP or external mail server using Exchange
Server's smart host feature. (Keep in mind that if you don't have a
commercial IP address, messages sent directly from your server may be
blocked by Real time block lists.)"
"While POP3 connectors are discouraged by most Exchange
administrators, if you are going to use external mailboxes it's much
better to use a connector and collect everyone's email from a central
point on a regular schedule, passing it through virus and anti-spam
scanners before depositing it in the Exchange mailboxes, rather than
each employee collecting their own email as often as they want."
1) You could use the SBS 2003 POP3 Connector tool
2) You could use some other POP3 Connector program
3) You could simply set the Exchange account as the default in Outlook
"It is widely known that Microsoft Exchange Server 2000/2003 doesn't
support receiving mail through the POP3 protocol. However, in
practice, it has been shown that many users find the absence of this
feature inconvenient. All the existing solutions entice users to use a
utility agent receiving mail through the POP3 protocol and delivering
it to the Exchange Server through the SMTP protocol. This is a
versatile solution equally usable for most SMTP-servers. However,
there are a number of negatives with this method... "
1) SBS POP3 Connector tool
How to?Get Connected With POP3
Already installed by default, you will access and configure the POP3
Connector using the following steps...
Install this patch before enabling the connector.
2) Other Connectors
Connecting Microsoft Exchange Server to a POP3 Account
All of the commercial POP3 connectors should be able to deliver mail
to any SMTP address, including mail-enabled Public Folders.
3) Exchange as Default
I hate Microsoft Exchange. Let me explain why.
"So far, I?ve found that Outlook - when configured to use Exchange and
a POP3 account - doesn?t like to send email through the default SMTP
server, say 'mail.company.com.' Instead, it just seems to ?forget?
that it?s supposed to use that server, and instead says 'oh, I?m
configured for Exchange - obviously they must?ve wanted to send it
through Exchange. I?ll just do that for you!'"
And then the Exchange server says 'wait a minute there, sparky. I?m
not relaying anything for you (even though I?ve been configured for
open relay and you?re properly authenticated). BOUNCE!'"
"I?ve never found a ?solution? for the problem; only a ?workaround.?
And like I said, the workaround is to make the Exchange account the
?default? account in Outlook, thus causing all outgoing mail to be
sent through Exchange (which will then forward it to your ?real? SMTP
server). Otherwise, it just doesn?t work."
"In the end, I had to switch everyone?s email settings to use the
Exchange server as the default for outgoing mail"
I hope this helps. If you have any questions, please post a
clarification request and wait for me to respond before closing/rating
Google Search Terms Used: exchange server outlook pop3 connector smtp bounce