cant send email between 2 domains

Posted on 2005-04-19
Last Modified: 2010-04-10
the company i work for has two domains ill refer to them as and In our office we host the Exchange server. Our ISP hosts a and which reside on the same server, I believe they are using qmail for their server. when sending email from to the email bounces back saying something along the lines of account not found. even though the account does exist on the exchange server at my office. the only workaround is that we add the same account to at the ISP. shouldn't the emails be coming to at the office first? this is the only domain that we have problems with. our exchange server at the office is used for correspondance everyday with many different domains, and none fail. the only conclusion that i could come to was that the at the ISP is acting like a domain controller and would have to mirror the user accounts at my office. we also use the email account as a fall back with a GFI pop2exchange connector, in case our link goes down. the only fix that i could think of was to move the domain off the same box as the is being hosted on. is this the right move? we want to fix this problem of not being able to send email between the domains and still keep our fault tolerance plan. thanks in advance for any responses.

Question by:AndyMagruder
    LVL 24

    Expert Comment

    If your ISP hosts, then it is to yours ISPs mail-server that these mails will first be deliverered.  You collect mail from there with the POP connector, as you say.  This means if the ISP does not have a mailbox for a user, the mail will be rejected.

    The way round this would be to ask your ISP if they can provide a Catch-all POP3 mailbox.  This is a mailbox that will accept any mail to the domain ( that is not accepted by another POP mailbox for that domain.  The easiest way I find to configure this kind of scenario is to simply have one catchall mailbox at the ISP, and use the Exchange POP connector (or in your case GFI Pop2Exchange, which I assume offer similar if not greater functionality) to collect all the mail and distribute it among your Exchange mailboxes accordingly.

    Author Comment

    Ok, Sorry if  I dont understand. What confuses me is that the only domain that we have an email problem with is the All other outside world domains are sent to my office ( just fine. I dont know if I had made this clear in the fact that we also host here at the office. Which *should* be considered the primary email server for, and it is acting like it for other emails just not the emails. The catch-all POP3 mailbox is a great idea for fault tolerance, but is this just a workaround, or an actual fix to the situation?


    LVL 24

    Accepted Solution

    Ok, I think I need a better understanding of your setup.

    You have two domains, does the domain and the domain use the same DNS server?  Or have the domain got it's own DNS server, and is it configured to forward requests to your ISP?  If it is configured to forward requests to your ISP, the chances are that when does an MX lookup for, it will be told that the MX is your ISPs server.

    If this is the case, another way around the problem would be to manually add a forwarder to the DNS server which would ensure that all requests that refer to the domain are in fact sent to your internal DNS server.  In that case, the MX returned would be the exchange machine.

    A manual forwarder can be set up by doing this on the DNS server for

    - Right-click on the server (in DNS Management) and click Properties
    - Select the "Forwarders" tab
    - Click "New", then type, followed by OK
    - Select from the list
    - Enter the IP address of's DNS server in the box below, and then click "Add"
    - Click Apply
    - You may want to restart the DNS server, but there should not be any need to do this.

    If the problem is what I think it is as described above, this should solve it.  Let me know!

    Featured Post

    NetScaler Deployment Guides and Resources

    Citrix NetScaler is certified to support many of the most commonly deployed enterprise applications. Deployment guides provide in-depth recommendations on configuring NetScaler to meet specific application requirements.

    Join & Write a Comment

    Suggested Solutions

    There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
    This is an article about my experiences with remote access to my clients (so that I may serve them) and eventually to my home office system via Radmin Remote Control. I have been using remote access for over 10 years and have been improving my metho…
    Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now