none
Delivery Failure Reason: 601 Attempted to send the message to the following ip's:

    Question

  • We have a client that is trying to send us emails but is getting a Delivery Failure notice in return. The client is sending the email to two of our users. Here is the contents of the email the client gets:

    Could not deliver message to the following recipient(s):
    
    Failed Recipient: user1@company.com
    Reason: Remote host said: 601 Attempted to send the message to the following
    ip's: 
    	107.1.0.0
    
    Failed Recipient: user2@company.com
    Reason: Remote host said: 601 Attempted to send the message to the following
    ip's: 
    	107.1.0.0
    
    
       -- The header and top 20 lines of the message follows --
    
    Received: from TSprague3 (UnknownHost [192.168.11.40]) by mail.clientcompany.com with SMTP;
       Mon, 4 Aug 2014 16:00:43 -0700
    From: "Customer" <customer@clientcompany.com>
    To: "'user1'" <user1@company.com>
    Cc: "'user2'" <user2@company.com>,
    References: <E338309C64548949BE5E77CD32EB61974C8E1489B6@company>
    <010501cf6e12$7249f570$56dde050$@clientcompany.com>
    <E338309C64548949BE5E77CD32EB61974C902F46E7@company>
    <012501cf6e16$c8872670$59957350$@clientcompany.com>
    <E338309C64548949BE5E77CD32EB61974C902F4EC8@company>
    <01c601cf6fb7$7a9e5990$6fdb0cb0$@clientcompanys.com>
    <E338309C64548949BE5E77CD32EB61974C92027132@company>
    <012b01cf79f8$d5ec57c0$81c50740$@clientcompanycom>
    <E338309C64548949BE5E77CD32EB61974C951C213F@company>
    <01d501cf94b8$e6bf3e20$b43dba60$@clientcompany.com>
    <E338309C64548949BE5E77CD32EB61974C951C2186@company>
    <CBD18B81-1A24-4C76-A68D-98A1D39968EB@clientcompany.com>
    <E338309C64548949BE5E77CD32EB61974C951C2999@company>
    <02cf01cf9fab$b5dfc9c0$219f5d40$@clientcompany.com>
    <01cd01cf9fb2$28a068b0$79e13a10$@clientcompany.com>
    <E338309C64548949BE5E77CD32EB61974C95B4B942@company>
    <E338309C64548949BE5E77CD32EB61974C986DFDC0@company>
    In-Reply-To: <E338309C64548949BE5E77CD32EB61974C986DFDC0@company>
    Subject: RE: Solimar Systems  |  CompView Audio Visual  -  ***Revised AV Proposal Attached***
    Date: Mon, 4 Aug 2014 16:00:44 -0700
    Message-ID: <01eb01cfb037$ebd66560$c3833020$@clientcompany.com>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
    	boundary="----=_NextPart_000_01EC_01CFAFFD.3F79B040"
    X-Priority: 1 (Highest)
    X-MSMail-Priority: High
    X-Mailer: Microsoft Outlook 15.0
    Thread-Index:
    AQGeEigjTE3UZNssSuz3xKuVnLMrcQInMcTnAka6MQUAwhIi6gJ0ajLhAm8h1m8CZ0UxDgE0HEzJ
    AfD1GSECGnkVvwInFXJNAwQEmz0CZSco+gM5acxjAfyELaMB41oXjwI0MAjImw+J3mA=
    Content-language: en-us
    Importance: High
    X-MessageSniffer-Identifier:
    D:\SmarterMail\Spool\SubSpool5\-1074803860273.eml
    X-GBUdb-Analysis: 0, 192.168.11.40, Ugly c=0.440712 p=-1 Source White
    X-MessageSniffer-Scan-Result: 0
    X-MessageSniffer-Rules:
    	0-0-0-32767-c
    
    This is a multipart message in MIME format.
    
    ------=_NextPart_000_01EC_01CFAFFD.3F79B040
    Content-Type: multipart/related;
    	boundary="----=_NextPart_001_01ED_01CFAFFD.3F79B040"
    
    
    ------=_NextPart_001_01ED_01CFAFFD.3F79B040
    Content-Type: multipart/alternative;
    	boundary="----=_NextPart_002_01EE_01CFAFFD.3F79B040"
    
    
    ------=_NextPart_002_01EE_01CFAFFD.3F79B040
    Content-Type: text/plain;
    	charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    
    Matt,
    
     
    
    They used to be emailing back and forth but all the sudden this client's emails started getting kicked back. Any ideas?


    Dan Chandler-Klein

    Wednesday, August 6, 2014 10:50 PM

Answers

  • Use "get-receiveconnector" for a list of all the connector names.

    I think, in your case, you've omitted the name of the server. Try using "servername\Internet SMTP 2007" as the "-Identity".


    --- Rich Matheisen MCSE&I, Exchange MVP

    Saturday, August 9, 2014 9:19 PM

All replies

  • Hi

    Firstly go to MXtoolbox.com and check that your IP is not blacklisted.

    Secondly, can you telnet on port 25 from your exchange server?

    Lastly, try increasing the smtp timeout and see if the mail goes through. are you having this problem all the time or just with this client?

    Any changes to firewalls recently or did you introduce any spam software etc.?

    Thursday, August 7, 2014 4:25 AM
  • - Firstly go to MXtoolbox.com and check that your IP is not blacklisted.

    Checked and I don't see it as being blacklisted. That said, I clicked the "find problems' button on there and it came up with a few issues:

    - Secondly, can you telnet on port 25 from your exchange server?

    I'm not quite sure how to do this. Do you mean telnet to their server from our Exchange server?

    Lastly, try increasing the smtp timeout and see if the mail goes through. 

    I will try this.

    - Are you having this problem all the time or just with this client?

    As far as I know, just this one client.

    Any changes to firewalls recently or did you introduce any spam software etc.?

    No, no changes. 

    Thanks for your help!


    Dan Chandler-Klein

    Thursday, August 7, 2014 2:08 PM
  • Where is the 601 status code defined in a SMTP RFC?

    Have the sending organization check their side for problems. There may be a routing problem (it wouldn't be the first time I've seen problems introduced by a misplace static route somewhere between two organizations). That 601 status is probably specific to whatever software they're using.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, August 7, 2014 3:09 PM
  • Where is the 601 status code defined in a SMTP RFC?

    I'm sorry, I don't know what you mean by this.

    I just looked through my Exchange message logs and it looks like it is hitting our server but I guess it is getting turned around?

    2014-08-06T22:55:25.887Z,,mailserver,,mailserver,,,STOREDRIVER,DELIVER,2499484,<022201cfb1c9$598931e0$0c9b95a0$@clientcompany.com>,user1@company.com;user2@company.com,,91529,2,,,RE: SA4666 Solimar Systems - CompView - AV Project,user1@clientcompany.com,user2@clientcompany.com,2014-08-06T22:55:25.215Z
    There are several places where I see entries similar to this in the log file.


    Dan Chandler-Klein


    • Edited by snipazer Thursday, August 7, 2014 3:16 PM
    Thursday, August 7, 2014 3:15 PM
  • I mean that 601 isn't a status code that I've seen defined in any RFC for the SMTP protocol -- at least not any RFC that Exchange claims it follows.

    FYI, you should be looking at the SMTP protocol logs, not the message tracking logs. If your server rejects a message it won't show up in the message tracking logs. If you have anything other than Exchange in your inbound mail stream you should check any log files they produce, too.

    Also, since the SENDER is reporting the error they should be able to tell you which MTA it was that sent that status code. It might be theirs. It might be a service they use. It might be some 3rd-party service or software that you're running, too.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Friday, August 8, 2014 2:51 PM
  • Hmmm, looks like our SMTP logging was not on. I used this command to turn it on:

    Set-RecieveConnector "Internet SMTP 2007" -ProtcolLoggingLevel verbose

    But I got this error in return:

    Set-ReceiveConnector : The operation could not be performed because object 'Int
    ernet SMTP 2007' could not be found on domain controller 'company.domaincontroller'.
    At line:1 char:21
    + Set-ReceiveConnector <<<<  "Internet SMTP 2007" -ProtocolLoggingLevel verbose
        + CategoryInfo          : NotSpecified: (0:Int32) [Set-ReceiveConnector],
       ManagementObjectNotFoundException
        + FullyQualifiedErrorId : 4EAFF826,Microsoft.Exchange.Management.SystemCon
       figurationTasks.SetReceiveConnector
    I'm not sure why it's looking for the connector on the domain controller...


    Dan Chandler-Klein

    Friday, August 8, 2014 3:04 PM
  • Use "get-receiveconnector" for a list of all the connector names.

    I think, in your case, you've omitted the name of the server. Try using "servername\Internet SMTP 2007" as the "-Identity".


    --- Rich Matheisen MCSE&I, Exchange MVP

    Saturday, August 9, 2014 9:19 PM