Why can't POP3 clients receive Exchange Server email?

I can run an nslookup command and successfully connect to the outside email server (mail.badmc.org). However, when I try to connect to the outside email server from my Microsoft Outlook POP3 client, I receive a message saying the server was found but did not respond. Can this be done?

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT POP3 Stop personal calendar appointments from showing on Exchange Server Email mistakenly marked as 'read' when received on BlackBerry devices Should I allow our BES to access my personal POP3 email account? Tools and methods for disabling IMAP and POP in Exchange Server 2003 Configure a mobile device to receive POP3 email from Exchange Server Email sent to a PDA doesn't get saved in Exchange Server mailbox Can I back up Exchange Server with a POP3 hosted email server? Set up Outlook to use POP3 email and Exchange calendars on Windows SBS Forward Exchange Server email to an ISP using Active Directory POP3 server filters all email into Junk folder as spam POP3 Research SMTP Changing email address formats in Exchange Server 2003 Exchange users receiving email addressed to legacy users Configure BES to direct email from a new domain email address Troubleshooting Microsoft Exchange Server Event ID error 6009 How to lock down an SMTP relay to prevent spam in Exchange Server 2003 Tool helps identify inbound Exchange Server email flow issues Configure SMTP relay restrictions in Exchange Server 2003 to stop spam Exchange email sent to a domain using SPF authentication is returned Exchange event sink scripting error when configuring email disclaimer Configure SMTP connection limits in Exchange Server 2003 and SBS Microsoft Exchange Server and DNS Configure BES to direct email from a new domain email address How to configure DNS records for Exchange Server on Windows SBS 2003 OWA stops working from external network connection Locate 'missing' SPF record on an external DNS domain Receiving 'failed MX lookup' delivery status notification IP address changes for an Exchange 2000 recovery server 0xC103FC93 error with Exchange 2003 setup and install Set up FQDN and bridgeheads for POP3 and IMAP4 email Reverse DNS mismatches mark Exchange email as spam New Exchange Server installation not receiving SMTP or POP3 email

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary POP3  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

If you have Microsoft Exchange deployed, you can have inbound mail delivered to Exchange mailboxes, rather than to your ISP. If users want to use POP3 clients to access their mailboxes, Exchange supports POP3. It's important to note that POP3 is a protocol to access email and mailboxes. POP3 clients use SMTP to send outbound mail to an SMTP server.

Not having a public external IP address complicates things a little. You can use a number of dynamic DNS services. These services install a light agent on the server, which connects to the DNS service provider and notifies it of its external IP address. The dynamic DNS provider updates the DNS zone for your domain with that IP address. This allows you to use MX records to receive inbound email, and also allows your POP3 clients, which are probably connecting from outside the firewall, to access your Exchange server using its fully qualified domain name (FQDN).

However, this arrangement becomes less practical in two scenarios:

1. If your ISP blocks the SMTP port, denying you the ability to send and receive mail using SMTP from a dynamic IP address to any other mail server on the Internet (except the ISP's own SMTP hosts). This is done for two reasons:
1. To deter spammers, and
2. To prevent customers using Internet connections generally meant for home use from using them as hosting servers. They want you to buy more expensive "business" connections. Nevertheless, you may find connections with at least one static IP address offered by your ISP at a nominal cost. If that's the case, I would recommend going with it.
2. Many mail systems, including those run by large service providers and Web-based email providers, block SMTP connections from dynamic IP addresses. Additionally, entire blocks of static IP addresses may be listed on some DNS Block Lists (RBLs).

Mixing an internal Exchange Server deployment with external ISP-hosted POP mailboxes adds more complications to your deployment. There are some POP3 connectors available for Exchange that allow your Exchange server to fetch users' mail from external POP3 mailboxes and deliver them to Exchange mailboxes, including the POP3 Connector available in Microsoft's Windows Small Business Server (SBS). I am not a big fan of these.

In your case, I would recommend getting Internet connectivity with a static external, public IP address if possible. If you do get one, simply point your MX record to your own external IP address.

If that's not possible, perhaps look at using your ISP as an SMTP relay.

Do you have comments on this Ask the Expert Q&A? Let us know.

Ask a Microsoft Exchange question in our IT forum.