Home > Ask the Microsoft Exchange Experts > Bharat Suneja: Server Administration Questions & Answers > Set up FQDN and bridgeheads for POP3 and IMAP4 email
Ask The Exchange Expert: Questions & Answers
EMAIL THIS

Set up FQDN and bridgeheads for POP3 and IMAP4 email

Bharat Suneja EXPERT RESPONSE FROM: Bharat Suneja

Pose a Question
Other Exchange Categories
Meet all Exchange Experts
Become an Expert for this site


Exchange Server tips, tutorials and expert advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


>
QUESTION POSED ON: 10 July 2007
We have POP3 and IMAP set up on our two bridgehead servers, and we have a fully qualified domain name (FQDN) set up in DNS (we'll use smtp.client.com for the example). This FQDN is pointed to one particular bridgehead.

When the client tries to access smtp.client.com, and the specific mailbox that he is trying to access is on the server to which the FQDN is pointing, the user can access POP3 and IMAP. However, if the FQDN is pointed to the other bridgehead server, which does not contain the actual mailbox, the client is unable to access the mailbox.

Is there a way to set up the FQDN to allow the users to always access any mailbox on any server? Which server does the FQDN need to point to for this to occur?

We have two front-end servers, about 15 routing groups, several bridgeheads for the routing groups, two main Internet gateways (one that's a primary inbound and one that's secondary using costs), and about 35 mailbox servers. We are almost completely migrated to Exchange Server 2003 Service Pack 2, with a couple of exceptions where the server is still Exchange 2000 Service Pack 3.



Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Microsoft Exchange Server and DNS
Configure BES to direct email from a new domain email address
Why can't POP3 clients receive Exchange Server email?
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
Reverse DNS mismatches mark Exchange email as spam
New Exchange Server installation not receiving SMTP or POP3 email

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?
Why can't POP3 clients receive Exchange Server email?
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 Research

IMAP
Tools and methods for disabling IMAP and POP in Exchange Server 2003
IMAP list command only returns a list of Exchange public folders
Lookout
Exchange Server and POP3 FAQs
A primer on messaging standards: SMTP, POP and IMAP
Changing mail to plain text
Relay prevention on the Exchange server
Configuring Exchange to send/receive mail through an ISP
Enable more services
Importing e-mails without third-party software
IMAP Research

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


From your description, it seems the users are trying to access mailboxes using POP3/IMAP4. The term "bridgehead" may be a little confusing in this context.

What we need to establish is whether the server to which the users connect (smtp.client.com) is a back-end server that hosts mailboxes or a front-end server, which does not host mailboxes. Both front-end servers and back-end servers can be bridgehead servers.

The term "bridgehead" simply means that the server has SMTP running, and email is being routed through it using a connector. For example, the SMTP virtual server on that Exchange server is explicitly selected as a bridgehead for a connector.

Now that we've got that out of the way, here are the two scenarios:

  1. If the server that POP3/IMAP4 clients connect to is a front-end server, it proxies users' requests to the back-end server(s) where the mailboxes reside. In this case, all users should be able to access their mailbox using POP3/IMAP4 protocols when connected to that server.
  2. However, if the server being connected to is a back-end server, it does not behave in that manner. This is perhaps why you're seeing some users, who have mailboxes hosted on that server, are able to access mailboxes, whereas users with mailboxes on other back-end servers cannot.
The solution: Have users connect to a front-end server instead. This can be done by allowing the appropriate protocol (POP3/IMAP4) traffic to it from the Internet (and additionally may require creation of an A record for that server's FQDN in your external DNS zone).

Also note that front-end servers can be used as bridgeheads if they're running SMTP. You can add them to connectors and also point your external MX records to these.

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

Related information from SearchExchange.com:

  • Tip: Messaging standards for SMTP, POP and IMAP
  • Tutorial: A primer on DNS and MX records
  • Tutorial: How to set up a front-end Exchange Server cluster
  • Primer: Exchange server roles and hardware requirements
  • Reference Center: Microsoft Exchange Server and DNS



  • Search and Browse the Expert Answer Center
    Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
    Browse our Expert Advice



    Outlook Web Access (OWA) Tips and Advice
    HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
    About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
    SEARCH 
    TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

    TechTarget Corporate Web Site  |  Media Kits  |  Site Map




    All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
      TechTarget - The IT Media ROI Experts