Announcement

Collapse
No announcement yet.

Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message exp

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

  • Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message exp

    We have been having an issue sending emails only to one domain, "@me.com". I have been searching but still can not find a resolve. It appears that the email just gets stuck in the queue and then times out with #550 4.4.7 QUEUE.Expired; message expired ##.

    I used the Message Flow tool to capture some screen shots to show what is taking place with an email that can be sent and then one that cannot be sent.

    I have attached those screenshots.

    Not sure what other information is needed.

    Server 2008 64-bit / Exchange 2007
    Send Connect with Address "*"

    Thanks,



    Attached Files

  • #2
    Re: Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message

    The screenshots don't really show much of any use.
    The primary reason for these kinds of errors is simply that your server cannot connect to the other server for some reason. That could be a DNS lookup error, a routing error, a problem with the servers talking to each other.

    Have you confirmed the domain has valid DNS records, that you can connect to the MX record host using telnet from the Exchange server?

    If everything appears correct, then in many cases I simply configure a Send Connector to route email for problematic domains via my ISPs SMTP Server.

    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: Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message

      Thanks for the reply. I did an nslookup from our network and I did come up with the correct SMTP for the "@me.com" domain.

      that you can connect to the MX record host using telnet from the Exchange server?
      I'm not an exchange admin by any means, I'll do some googling.

      simply configure a Send Connector to route email for problematic domains via my ISPs SMTP Server.
      I was actually looking to do this but I'm not sure how I would configure another send connector without interrupting the rest of our outgoing emails.

      If my only problem domain is @me.com domain and I know the smtp server, just not sure how I would set this send connector for only emails that are going to the me.com domain.

      I would appreciate any assistance with the new send connector.

      Thanks,

      Comment


      • #4
        Re: Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message

        Change the cost on the existing connector to 2.
        Create a new SMTP connector using the New Connector wizard. Set the address space to be the domain you are having problems with, and then set it to use a smart host and enter your ISPs SMTP Server. 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


        • #5
          Re: Unable to Send an email to a specific domain - #550 4.4.7 QUEUE.Expired; message

          Well I figured it out. turns out it was OpenDNS, I wound have never figured it out unless I had a buddy double check the smtp IP address of the Mobile Me smtp address. I was having telnet issues with both the name and IP address so I called a buddy to check it from his server and he got connected, I told him the steps I was doing and then he questioned my IP address, as soon as I put in the IP in google, it came up with OpenDNS server IP. I added "@me.com" as allowed and then everything started working fine.

          Crazy.

          Thanks for the help.

          Comment

          Working...
          X