Question

  • Creator
    Topic
  • #2223430

    Exchange can’t send e-mails to domains registered with godadday.com

    Locked

    by jm ·

    Our Exchange Server (5.5) can’t send e-mails to domains registered with godadday.com. It appears to believe they are internal addresses. As soon as a user sends or replies to an e-mail, he get’s this message:
    Your message did not reach some or all of the intended recipients.

    Subject: FW: Hey
    Sent: 11/20/2007 10:35 AM

    The following recipient(s) could not be reached:

    ‘??????@godaddy.com’ on 11/20/2007 10:35 AM
    The recipient name is not recognized
    The MTS-ID of the original message is: c=US;a= ;p=MMMail;l=MM_SRV-071120163438Z-36085
    (Please note that I replaced the real name with ??????)

    This happens with any domain that was registered with Go Daddy. How do I force it to recognize these as an external address? Our domain controller (different machine than Exchange server) is also the DNS server for our network.

All Answers

  • Author
    Replies
    • #2481243

      Clarifications

      by jm ·

      In reply to Exchange can’t send e-mails to domains registered with godadday.com

      Clarifications

    • #2481240

      Upgrade your Exchange Server

      by sscribner ·

      In reply to Exchange can’t send e-mails to domains registered with godadday.com

      Its quick, Its Easy and it will solve your problem.

    • #2481239

      re: rejection from godaddy.com

      by thumbsup2 ·

      In reply to Exchange can’t send e-mails to domains registered with godadday.com

      That is an email rejection FROM godaddy.com telling you that the recipient does not exist. People who register for an email account at godaddy.com receive a personalized email address which does NOT end with godaddy.com. Godaddy says this:

      It offers unique you@YourPersonalDomainName.com personalization.

      It also has SPAM protection built in. You might actually get yourself blacklisted.

      And, the rejections you are seeing might not have even originated on your server. It’s entirely possible that someone is spoofing your email address to send spam and the rejections are being returned to you.

      • #2481232

        No this was an internal message.

        by jm ·

        In reply to re: rejection from godaddy.com

        The godaddy.com address in the post was to one of their tech support staff. The other addresses were to domains that were registered through godaddy according to a WHOIS lookup.

    • #2481208

      Thumbsup is right

      by cg it ·

      In reply to Exchange can’t send e-mails to domains registered with godadday.com

      godaddy.com sent your email server a message indicating that said recipient on the email you sent it could not be found.

      The return message isn’t an internal message meaning that your exchange server is the originating server.

      so the ????? isn’t in godaddy.com’s global distribution listing.

      • #2481197

        Nope, still not an external reply

        by jm ·

        In reply to Thumbsup is right

        These messages never went to Exchange’s Internet Mail Connector. Also, the error message is from our internal system administer account and there are no internet headers on this message. The other e-mails were to different domains and the address listed in the error was the one used in the original message. I only used the godaddy.com tech support address because I didn’t want to use our vendors’ real domains. I’m the one who changed the name to ?????. Trust me when I say, this is an internal system administrator reply.

        • #2481195

          can you ping said domain?

          by thumbsup2 ·

          In reply to Nope, still not an external reply

          Can you ping your vendor’s real domain? Or Tracert? If a DNS server somewhere between you and them is down and you can’t get to it with ping, your exchange server will know it.

        • #2481190

          ok godaddy.com is the example

          by cg it ·

          In reply to Nope, still not an external reply

          well ok but please make that apparent. your initial question was written to sound like godaddy.com is bouncing emails back.

          Thumbsup is correct again in that if DNS in the mix is down, Exchange knows DNS is down or that DNS can not forward an external request.

Viewing 3 reply threads