Announcement

Collapse
No announcement yet.

Mailbox Unavailable on New Exchange Setup

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mailbox Unavailable on New Exchange Setup

    All:

    I am working on setting up exchange 2010 in a sandbox environment and I am having some trouble. At this point we have installed exchange on our test server and are able to have a client connect through outlook 2010. We have send connectors setup as we are not intenting to use an edge transport server.

    We are able to send email from the client computer to external emails. However, when testing emails coming into our organization, we are receiving 550 error messages statign that the "mailbox is unavailable". I have tested doing a telnet with the server and we are able to deliver mail manually through the process outlined here: http://support.microsoft.com/kb/153119

    I have checked permissions on the receive connector to ensure that anonymous users have permission to send to our server.

    Any suggestions as to why we cannot receive mail from external soruces would be apprecaited.

  • #2
    Re: Mailbox Unavailable on New Exchange Setup

    Did you create new connectors or modify the default? The default connector is all that you need to change, just enable Anonymous and then restart Transport. Job done.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Mailbox Unavailable on New Exchange Setup

      I have modified both the default and client receive connectors to include permissions groups of "anonymous, exchange users, exchangge servers and legacy exchange servers" checked. I had not restarted the server so I thought that would solve my problem but no luck.

      I should make you aware that email is being sent to an authoritative domain different from the domain the server is on, if that matters.

      Comment


      • #4
        Re: Mailbox Unavailable on New Exchange Setup

        Exchange doesn't care about the WINDOWS domain. As long as you have configured the domain in Accepted Domains correctly and the correct email address is on the user account, then that should be all that is required.
        Changing the Client Connector was completely unnecessary and I would suggest that you put the settings back to the default.

        If the traffic works on telnet, then that would start to pint to the issue being outside of Exchange. There should be no difference between a telnet connection and a regular delivery from another host. Therefore I would be looking at things like MX records, and anything between Exchange and the Internet for the source of the issue.

        Have you tried any of the Internet based email verification tools? They can show you how the traffic is being answered which can often tell you if exchange is answering the SMTP traffic or not.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Mailbox Unavailable on New Exchange Setup

          I will change the client connector back to the default settings. After looking at my firewall settings, it seems the messages are being received, filtered and forwarded to the exchange server.

          With regard to your queastion about the MX records, I have setup an A record of mail.ourdomain.com to forward to our external IP. Since this is only my sandbox, I have been sending emails to [email protected]. Since the firewall seems to be filtering it, I assume this is working.

          I have not tried the internet based tools, are you referring to the ones installed with exchange? Or some third party website? Which ones would you recommend starting with?

          Comment


          • #6
            Re: Mailbox Unavailable on New Exchange Setup

            If you only have one external IP address and you have a live server on the end of it, then that is going to be a problem for you.
            As far as the Internet is concerned, user @ example.com and user @ mail.example.com are two different domains. If you want email to be received by another server then you are going to need to have either two IP addresses or the server that is Internet facing is going to have to be configured to send email to the second server. There are no other options.

            Simon.
            --
            Simon Butler
            Exchange MVP

            Blog: http://blog.sembee.co.uk/
            More Exchange Content: http://exchange.sembee.info/
            Exchange Resources List: http://exbpa.com/
            In the UK? Hire me: http://www.sembee.co.uk/

            Sembee is a registered trademark, used here with permission.

            Comment


            • #7
              Re: Mailbox Unavailable on New Exchange Setup

              Our current scenario is that we have another company hosing our mail. The current MX records point to the their party servers. I setup an A record of "mail.ourdomain.com" pointing to the external IP of our company.

              In order to test and not disrupt the current mail activity, I have been sending emails to [email protected] with the hope of testing the exchange setup on our premisis and now interrupting normal mail flows. Since I see the email hitting our firewall, I am guessing that this work. Is exchange getting confused because there is no mail.ourdomain.com and it is only expecting to see ourdomain.com?

              If I setup a new MX record with the same preference as our their party, mail should be delivered to both our test setup and the their party company right? Is that the way to go here in terms of testing?

              Comment


              • #8
                Re: Mailbox Unavailable on New Exchange Setup

                If you want to send email to mail.example.com then you will need a complete ZONE for mail.example.com, which you can put a host name and MX record in to. Just setting up mail.example.com as a host and sending to that isn't going to work in any reliable manner. I expect it is only partially working now because of the lack of MX records and something is falling back to another type of configuration, but that isn't how SMTP is designed to work.

                With regards to a second MX record, they do not work in the way that you have imagined. If you have two MX records in your domain then the email for the domain could be sent to either server (technically the cost controls which server they are sent to, but I don't see cost is used much now).

                If you want to test Exchange and you cannot setup a complete zone, then either register a second domain or use a dynamic DNS service. I know that Dyn.com will setup a host and MX records for you so that you can receive email on the dynamic DNS host name correctly. Of course it will also need to be listed in your Accepted Domains list.

                Simon.
                --
                Simon Butler
                Exchange MVP

                Blog: http://blog.sembee.co.uk/
                More Exchange Content: http://exchange.sembee.info/
                Exchange Resources List: http://exbpa.com/
                In the UK? Hire me: http://www.sembee.co.uk/

                Sembee is a registered trademark, used here with permission.

                Comment


                • #9
                  Re: Mailbox Unavailable on New Exchange Setup

                  Yep that was it!

                  I setup a full DNS record for the MX and I am now getting mail to our server. Thanks for the help. I guess trying the mail.ourdomain.com thing was only half working. And here I thought I had a good idea.

                  Comment

                  Working...
                  X