none
Cannot send mail to specific domain

    Question

  • Hi Guys

    We're using Exchange 2013 and we're having a problem where we're completely unable to send any mails to 1 specific domain. We get bounce backs saying unable to deliver but will keep trying, and eventually get:

    Diagnostic information for administrators:
    Generating server: REMOVED
    Total retry attempts: 190
    REMOVED
    Remote Server returned '550 4.4.7 QUEUE.Expired; message expired'
    Original message headers:
    Received: from REMOVED by REMOVED
    (10.0.0.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Dec 2015
    14:33:14 +0000
    Received: from REMOVED ([::1]) by REMOVED ([::1])
    with mapi id 15.00.1104.000; Wed, 9 Dec 2015 14:33:14 +0000
    From: Sender
    To: Recipient
    Subject: RE: Blocking
    Thread-Topic: Blocking
    Thread-Index: AdEyjlFXWf+hfTFkR16j7SdFhr2+0AAADMhQ
    Date: Wed, 9 Dec 2015 14:33:13 +0000
    Message-ID: REMOVED
    References: REMOVED
    In-Reply-To: REMOVED
    Accept-Language: en-GB, en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator:
    x-ms-exchange-transport-fromentityheader: Hosted
    x-originating-ip: [10.0.1.113]
    Content-Type: multipart/related;
            boundary=REMOVED
            type="multipart/alternative"

    MIME-Version: 1.0

    When checking Exchange Queue Viewer the message in the queue has the error

    Last Error: 451 4.7.0 Recipient rejected (R20)

    I've removed any identify data from the above.

    Have been in touch with the IT guys of the company we're trying to contact and they assure us that they can't see any issues on their side. We don't have any issues sending mail to any other domains.

    Do you have any ideas on what may be causing this issue, let me know what other info you need and i will try to provide it.

    Thanks

    Monday, January 4, 2016 1:17 PM

Answers

  • Thanks everyone for your help. SPF records are all correctly setup, turns out we were on an obscure blacklist. Strange thing is that the responses we were getting didn't mention the blacklist, and we didn't come up on any of the internet blacklist checks i was doing.

    Fixed it by accident in the end, we had another mail address that we couldn't get through to but this time the response mentioned that we were blacklisted. Contacted the holder to get removed and both addresses started working.

    Tuesday, January 12, 2016 2:50 PM

All replies

  • Hi,

    so the server, who is rejecting the mail, is the server from the other company?

    In this case, there is not much you can do, unfortunately....

    Kind Regards,

    Sebastian


    Best Regards, Sebastian

    Monday, January 4, 2016 2:01 PM
  • Can they trace any message from you at all?

    451 error is usually error on the other side, so not yours.

    You can check if your domain/ ip is on blacklist here: http://mxtoolbox.com/blacklists.aspx

    From your side, you can check get-queue and get-message in exchange powershell to see if you have high queues.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Monday, January 4, 2016 2:02 PM
  • If you mean this part, then it's from our own mail server.

    Received: from REMOVED by REMOVED
    (10.0.0.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 9 Dec 2015
    14:33:14 +0000
    Received: from REMOVED ([::1]) by REMOVED ([::1])


    Monday, January 4, 2016 2:34 PM
  • It's complicated like this ;)

    You should replace the different servers by different names, like "removed-external" and "removed-internal".


    Best Regards, Sebastian

    Monday, January 4, 2016 2:36 PM
  • :) Fair enough, here is another one that i've edited better

    Delivery has failed to these recipients or groups:
    RECIPIENT (RECIPIENT)
    The server has tried to deliver this message, without success, and has stopped trying. Please try sending this message again. If the problem continues, contact your helpdesk.


    Diagnostic information for administrators:
    Generating server: REMOVED INTERNAL
    Total retry attempts: 190
    RECIPIENT
    Remote Server returned '550 4.4.7 QUEUE.Expired; message expired'
    Original message headers:
    Received: from REMOVED INTERNAL (10.0.0.28) by REMOVED INTERNAL
     (10.0.0.28) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 14 Dec 2015
     13:23:54 +0000
    Received: from REMOVED INTERNAL ([::1]) by REMOVED INTERNAL ([::1])
     with mapi id 15.00.1104.000; Mon, 14 Dec 2015 13:23:54 +0000
    From: "SENDER" <SENDER>
    To: "RECIPIENT" <RECIPIENT>
    Subject: Email Attempt
    Thread-Topic: Email Attempt
    Thread-Index: AQHRNnKd7BoHOTqMNke49pxvnc4/5g==
    Date: Mon, 14 Dec 2015 13:23:54 +0000
    Message-ID: <1450099434435.28447@internal address>
    Accept-Language: en-GB, en-US
    Content-Language: en-GB
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    x-ms-exchange-transport-fromentityheader: Hosted
    x-originating-ip: [10.0.1.54]
    Content-Type: multipart/alternative;
            boundary="_000_145009943443528447internal_"
    MIME-Version: 1.0


    Monday, January 4, 2016 2:42 PM
  • This is the error from Exchange 2013 Queue Viewer for the mail

    Identity: IINTERNAL\70164\18279380812225
    Subject: Email
    Internet Message ID: <76b51c194bac460a9ec1b7094031ebc6@internaladdress>
    From Address: SENDER
    Status: Retry
    Size (KB): 9
    Message Source Name: SMTP:Default INTERNAL
    Source IP: 10.0.0.28
    SCL: -1
    Date Received: 04/01/2016 13:49:30
    Expiration Time: 06/01/2016 13:49:30
    Last Error: 451 4.7.0 Recipient rejected (R20)
    Queue ID: INTERNAL\70164
    Recipients:  RECIPIENT;3;2;[{LRT=};{LED=451 4.7.0 Recipient rejected (R20)};{FQDN=};{IP=}];0;

    Monday, January 4, 2016 2:46 PM
  • Thanks. :-)

    What concerns me there, is that only your server is mentioned, and your server is generating the error. So for any reason, the remote server does not accept mail from your server.

    Your Exchange is directly sending the mail to the internet?

    Can you try MS remote connectivity analyzer (https://testconnectivity.microsoft.com/)?


    Best Regards, Sebastian

    Monday, January 4, 2016 2:48 PM
  • This has only been an issue since we recently moved office. At the old location we could send emails to this server without issue, since we moved and now have a different ip this problem has occurred, albeit only with this one remote server.

    We're not using a smarthost and connectivity analyser is fine except it can't find an SPF record, we do have one however.

    Monday, January 4, 2016 2:55 PM
  • Could you then please check your SPF record and update it accordingly? I think it has to do something with the IP change. 

    All tests are green with Microsoft, except the SPF record?


    Best Regards, Sebastian

    Monday, January 4, 2016 2:57 PM
  • Yes, everything is green except the SPF record. This has been changed since we moved and is correct if i do an nslookup. MXToolbox.com also detects it correctly.
    Monday, January 4, 2016 3:06 PM
  • But something seems still to be wrong, what's the issue in the MS connectivity analyzer?

    Best Regards, Sebastian

    Monday, January 4, 2016 3:11 PM
  • This is the result from the SPF part of the analyzer

    Attempting to find the SPF record using a DNS TEXT record query.
      The Microsoft Connectivity Analyzer wasn't able to find the SPF record.
     
    Additional Details
     
    Text records were found, but the Microsoft Connectivity Analyzer couldn't find any SPF records.

    Monday, January 4, 2016 3:18 PM
  • Result from kitterman.com SPF search

    SPF record lookup and validation for: DOMAIN

    SPF records are published in DNS as TXT records.

    The TXT records found for your domain are:
    v=spf1 mx:********* ip4:********* -all 

    Checking to see if there is a valid SPF record. 

    Found v=spf1 record for INTERNAL: 
    v=spf1 mx:********* ip4:********* -all 

    evaluating...
    Results - record processed without error.

    The result of the test (this should be the default result of your record) was, pass . The explanation returned was, sender SPF authorized


    Monday, January 4, 2016 3:26 PM
  • If your domain is "contoso.com" and the public IP, which your mailserver is using to send mail out to the internet is "10.0.0.1/32", then your SPF should look like this:

    contoso.com.  IN TXT "v=spf1 mx ip4:10.0.0.1/32 ~all"

    Can you please go to http://www.spfwizard.net/ and enter all the details to put /verify the correct SPF record?

    Thanks.


    Best Regards, Sebastian

    Tuesday, January 5, 2016 6:17 AM
  • Hi IntouchGames,

    Open a telnet session from your Exchange server to the other company's public IP.

    Do a mail from, rcpt to test manually see the response.

    Eg. gmail.com = 64.233.169.27

    telnet 64.233.169.27 25

    EHLO Example.com MAIL FROM:<supertool@source.com> RCPT TO:<test@destiantion.com> Subject: Test Data This is a test body .



    Regards,

    Satyajit

    Please“Vote As Helpful” if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.



    • Edited by Satyajit321 Tuesday, January 5, 2016 10:00 AM
    Tuesday, January 5, 2016 9:59 AM
  • Make sure you've correctly define your MX FQDN and IP address in SPF record. If it is configured as hard fail -all try setting it up as ~all soft fail.

    Also make sure PTR record exists for your IP address.

    Please mark as helpful if you find my contribution useful or mark as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! ~eff~

    Wednesday, January 6, 2016 11:51 PM
  • Thanks everyone for your help. SPF records are all correctly setup, turns out we were on an obscure blacklist. Strange thing is that the responses we were getting didn't mention the blacklist, and we didn't come up on any of the internet blacklist checks i was doing.

    Fixed it by accident in the end, we had another mail address that we couldn't get through to but this time the response mentioned that we were blacklisted. Contacted the holder to get removed and both addresses started working.

    Tuesday, January 12, 2016 2:50 PM
  • Sorry, but which site were you blacklisted on?  I'm having the same problem but can't find any blacklisted site.
    Monday, February 8, 2016 10:12 PM