none
Intermittent incoming email issue - Invalid Domain

    Question

  • Hi,

    I have an issue with external emails coming into my exchange server sometimes returning non existent domain errors. The issue is intermittent and random. I have looked at the logs to try and understand what is happening, and my hunch is that it's either to do with high memory utilisation of my host servers from my virtual machines (since a previous issue described here had this as a possible cause), OR something to do with ipv6 dns lookup perhaps (in the logs as seen below, it says the dns lookup was performed by an ipv6 dns address). I say so since I've come across this being a possible cause from a number of sources online.

    DNS servers for my exhchange config are set as my two internal dns servers for primary and alternate.

    Can you take a look and let me know your thoughts?

    Thanks

    The domain name in the email address is incorrect. Check the address. 

    Diagnostic information for administrators:

    Generating server: ex-mb1.xxxx.com

    ahmed.omer@xxxx.com
    #554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##


    2017-04-26T08:09:49.288Z,08D48C331781EB2A,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,+,EX-MB1.xxxx.com
    2017-04-26T08:09:50.957Z,08D48C331781EB2B,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:09:54.716Z,08D48C331781EB2B,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB1.xxxx.com:InfoDomainNonexistent; EX-MB2.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:09:54.716Z,08D48C331781EB2B,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:09:54.966Z,08D48C331781EB2C,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:09:54.966Z,08D48C331781EB2C,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB1.xxxx.com:InfoDomainNonexistent; EX-MB2.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:09:54.966Z,08D48C331781EB2C,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:09:55.013Z,08D48C331781EB2A,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,>,"Failed; HResult: 5; DiagnosticInfo: Stage:CommitMailItem, SmtpResponse:554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain; Stage:GenerateNdr, SmtpResponse:"
    2017-04-26T08:09:55.013Z,08D48C331781EB2A,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,-,RegularSubmissions: 0 ShadowSubmissions: 0 Bytes: 0 Recipients: 0 Failures: 1 ReachedLimit: False Idle: False
    2017-04-26T08:11:39.812Z,08D48C331781EB2D,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,+,EX-MB1.xxxx.com
    2017-04-26T08:11:39.828Z,08D48C331781EB2E,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:11:39.828Z,08D48C331781EB2E,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB2.xxxx.com:InfoDomainNonexistent; EX-MB1.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:11:39.828Z,08D48C331781EB2E,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:11:39.828Z,08D48C331781EB2F,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:11:39.828Z,08D48C331781EB2F,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB2.xxxx.com:InfoDomainNonexistent; EX-MB1.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:11:39.828Z,08D48C331781EB2F,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:11:39.828Z,08D48C331781EB2D,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,>,"Failed; HResult: 5; DiagnosticInfo: Stage:CommitMailItem, SmtpResponse:554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain; Stage:GenerateNdr, SmtpResponse:"
    2017-04-26T08:11:39.828Z,08D48C331781EB2D,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,-,RegularSubmissions: 0 ShadowSubmissions: 0 Bytes: 0 Recipients: 0 Failures: 1 ReachedLimit: False Idle: False
    2017-04-26T08:13:39.464Z,08D48C331781EB30,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,+,EX-MB1.xxxx.com
    2017-04-26T08:13:39.479Z,08D48C331781EB31,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:13:45.719Z,08D48C331781EB31,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB1.xxxx.com:InfoDomainNonexistent; EX-MB2.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:13:45.719Z,08D48C331781EB31,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:13:45.719Z,08D48C331781EB32,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-04-26T08:13:45.719Z,08D48C331781EB32,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB2.xxxx.com:InfoDomainNonexistent; EX-MB1.xxxx.com:InfoDomainNonexistent;
    2017-04-26T08:13:45.719Z,08D48C331781EB32,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-04-26T08:13:45.719Z,08D48C331781EB30,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,>,"Failed; HResult: 5; DiagnosticInfo: Stage:CommitMailItem, SmtpResponse:554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain; Stage:GenerateNdr, SmtpResponse:"
    2017-04-26T08:13:45.719Z,08D48C331781EB30,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,-,RegularSubmissions: 0 ShadowSubmissions: 0 Bytes: 0 Recipients: 0 Failures: 1 ReachedLimit: False Idle: False
    Wednesday, April 26, 2017 11:04 AM

All replies

  • You might want to enable protocol logging on the appropriate receive connector(s) and see what's actually being presented to the server.

    Is there anything between the Internet and the Exchange server?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, April 27, 2017 7:12 AM
    Moderator
  • Hi Ahmeds,

    Except the suggestion above, you can also refer to the following similar threads and check if get any hints:

    Windows server network interface priority, DNS and Exchange “554 5.4.4”

    554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain in Exchange 2013

    Best Regards,


    Niko Cheng
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 27, 2017 9:27 AM
    Moderator
  • Hi Ed,

    Protocol logging is enabled, as far as I know. Part of the info I pasted above is from the logging (unless I have something totally different in mind! Sorry, I'm a bit new to this).

    Nothing between internet and exchange server.

    Thanks for your response.

    Thursday, April 27, 2017 11:06 PM
  • In the protocol logs, look for the MAIL FROM and RCPT TO entries to see to whom the message is actually addressed.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, April 27, 2017 11:19 PM
    Moderator
  • Hi Niko,

    Thanks for your response. I followed the steps in the two links but unfortunately still have the issue.

    What's frustrating is that it is intermittent/random...say I send emails from my yahoo/gmail/hotmail accounts it will get a bounceback say 1 out of 7 attempts.

    Thursday, April 27, 2017 11:22 PM
  • Can you direct me to which logs exactly I'd find those.

    Thanks

    Thursday, April 27, 2017 11:49 PM
  • The SMTP protocol logs.  Normally you'd find them under C:\Program Files\Microsoft\Exchange Server\V15TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive and ...\SmtpSend.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Friday, April 28, 2017 12:16 AM
    Moderator
  • Hi Ed,

    Some info to share for an email which bounced back yesterday:

    This is from the sender's end:

    Reporting-MTA: dns;ex-mb1.xxxx.com
    Received-From-MTA: dns;delivery.mailspamprotection.com
    Arrival-Date: Tue, 2 May 2017 16:02:58 +0000

    Final-Recipient: rfc822;ahmed.omer@xxxx.com
    Action: failed
    Status: 5.4.4
    Diagnostic-Code: smtp;554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain

    This is from the SmtpReceive

    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,39,192.168.1.6:25,108.178.24.182:60517,<,MAIL FROM:<wail@grand-eng.com> SIZE=6086542,
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,40,192.168.1.6:25,108.178.24.182:60517,*,08D49161AC02C675
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,41,192.168.1.6:25,108.178.24.182:60517,<,RCPT TO:<ahmed.omer@xxxx.com>,
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,42,192.168.1.6:25,108.178.24.182:60517,<,DATA,
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,43,192.168.1.6:25,108.178.24.182:60517,>,250 2.1.0 Sender OK,
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,44,192.168.1.6:25,108.178.24.182:60517,>,250 2.1.5 Recipient OK,
    2017-05-02T16:02:48.096Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,45,192.168.1.6:25,108.178.24.182:60517,>,354 Start mail input
    2017-05-02T16:02:51.731Z,WEBMAIL\Default Frontend WEBMAIL,08D49161AC02C675,46,192.168.1.6:25,108.178.24.182:60517,*,,Proxy destination(s) obtained from OnProxyInboundMessage event

    This is from SmtpSend

    2017-05-02T16:02:57.955Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,50,192.168.1.6:22517,192.168.1.3:25,>,MAIL FROM:<wail@grand-eng.com> SIZE=0 AUTH=<>,
    2017-05-02T16:02:57.955Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,51,192.168.1.6:22517,192.168.1.3:25,>,RCPT TO:<ahmed.omer@xxxx.com>,
    2017-05-02T16:02:58.720Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,52,192.168.1.6:22517,192.168.1.3:25,<,250 2.1.0 Sender OK,
    2017-05-02T16:02:58.720Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,53,192.168.1.6:22517,192.168.1.3:25,<,250 2.1.5 Recipient OK,
    2017-05-02T16:02:58.720Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,54,192.168.1.6:22517,192.168.1.3:25,>,DATA,
    2017-05-02T16:02:58.720Z,Inbound Proxy Internal Send Connector,08D49161AC02C676,55,192.168.1.6:22517,192.168.1.3:25,<,354 Start mail input
    2017-05-02T16:03:31.121Z,Inbound Proxy Internal Send Connector,08D49161AC02C678,0,,192.168.1.4:25,*,,attempting to connect

    This is an extract from Connect Log (in Connectivity/Submission). This does not correspond to the email above, but it is the error message we are seeing from the sender's end, so thought it might be helpful here

    2017-05-02T01:04:35.964Z,08D490B7A5250338,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,+,EX-MB1.xxxx.com
    2017-05-02T01:04:35.979Z,08D490B7A5250339,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-05-02T01:04:39.723Z,08D490B7A5250339,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB1.xxxx.com:InfoDomainNonexistent; EX-MB2.xxxx.com:InfoDomainNonexistent;
    2017-05-02T01:04:39.723Z,08D490B7A5250339,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-05-02T01:04:39.723Z,08D490B7A525033A,SMTP,mailboxtransportsubmissioninternalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
    2017-05-02T01:04:39.723Z,08D490B7A525033A,SMTP,mailboxtransportsubmissioninternalproxy,>,Non-existent domain reported by fe80::3e47:11ff:fe36:264e%12. [Domain:Result] = EX-MB2.xxxx.com:InfoDomainNonexistent; EX-MB1.xxxx.com:InfoDomainNonexistent;
    2017-05-02T01:04:39.723Z,08D490B7A525033A,SMTP,mailboxtransportsubmissioninternalproxy,-,Messages: 0 Bytes: 0 (The domain name does not exist. Please correct the address and try again.)
    2017-05-02T01:04:39.723Z,08D490B7A5250338,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,>,"Failed; HResult: 5; DiagnosticInfo: Stage:CommitMailItem, SmtpResponse:554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain; Stage:GenerateNdr, SmtpResponse:"
    2017-05-02T01:04:39.723Z,08D490B7A5250338,MapiSubmission,5fce9542-8dc3-4f71-967b-f4383a4b21c4,-,RegularSubmissions: 0 ShadowSubmissions: 0 Bytes: 0 Recipients: 0 Failures: 1 ReachedLimit: False Idle: False

    Also below are a couple of error message I spotted in the SmtpSend logs. Not sure if they are relevant to the issue at hand, but I'm trying to include as much info as possible

    2017-05-02T17:20:47.762Z,Client Proxy Send Connector,08D49161AC02C6AD,1,,192.168.1.3:465,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 192.168.1.3:465"

    2017-05-02T17:16:33.667Z,Client Proxy Send Connector,08D49161AC02C6A9,1,,192.168.1.3:465,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.3:465"

    Any help would be appreciated.

    Thanks

    Wednesday, May 3, 2017 7:54 AM
  • This is more detail from what is bouncing back to the sender:

    Diagnostic information for administrators:

    Generating server: ex-mb1.xxxx.com

    ahmed.omer@xxxx.com #554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##

    Original message headers:

    Received: from WEBMAIL.xxxx.com (192.168.1.6) by ex-mb1.xxxx.com
     (192.168.1.3) with Microsoft SMTP Server (TLS) id 15.0.516.32; Tue, 2 May
     2017 19:02:58 +0300
    Received: from delivery.mailspamprotection.com (108.178.24.182) by
     WEBMAIL.xxxx.com (192.168.1.6) with Microsoft SMTP Server (TLS) id
     15.0.516.32 via Frontend Transport; Tue, 2 May 2017 19:02:48 +0300
    Received: from ns1.es26.siteground.eu ([77.104.147.176]
     helo=es26.siteground.eu)      by se1.mailspamprotection.com with esmtps
     (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)    (Exim 4.86)    (envelope-from
     <wail@grand-eng.com>) id 1d5aFT-0005Sw-1h    for ahmed.omer@xxxx.com; Tue, 02
     May 2017 11:02:39 -0500
    DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
            d=grand-eng.com; s=dkim;
     h=Content-Type:MIME-Version:Message-ID:Date:Subject:
            In-Reply-To:References:To:From;
            bh=cHn+DICTiPSnB9GBs2lAYa/uCqiQSmHoiVFZcgoq9qs=;
     b=oIgAeNTlv4QhxrPE5qgjCDm8+H
            k3N+rc9AThwW+i+iYUm0lamr3LICnuQyxZPAlOkMM+TwajlpLxGHfvJNxdo/eZdwuJ4fEYsEEhvWh
            KA0okY9LQ1PANlY45ZcpoczSqBVYAyRi5g/Id7RycNUfaDQbhUHP328ktaU5PFKdyxSk=;
    Received: from [41.209.97.248] (port=49729 helo=adminPC)     by es26.siteground.eu
     with esmtpa (Exim 4.86_2)     (envelope-from <wail@grand-eng.com>)  id
     1d5aCl-0007Jv-Sm      for ahmed.omer@xxxx.com; Tue, 02 May 2017 18:01:54 +0200
    From: Wail Musa <wail@grand-eng.com>
    To: <ahmed.omer@xxxx.com>
    References: <CAP625P+dJOd94oxjbPLY_CH3y4EmH5M=pAPZ9f94cfLp8b4imQ@mail.gmail.com>
     <ab273215.1d2c356.1b65adf.4fe1@iesbiogas.mail>
     <CAP625P+aTOY3GqKBWd3odVxJYA3CTrQsYBb5RG+xv=SzzeSTng@mail.gmail.com>
    In-Reply-To: <CAP625P+aTOY3GqKBWd3odVxJYA3CTrQsYBb5RG+xv=SzzeSTng@mail.gmail.com>
    Subject: FW: R: Sudan Biogas project
    Date: Tue, 2 May 2017 18:59:11 +0300
    Message-ID: <000d01d2c35d$0acb5bc0$20621340$@grand-eng.com>
    MIME-Version: 1.0
    Content-Type: multipart/mixed;
            boundary="----=_NextPart_000_000E_01D2C376.301CB270"
    X-Mailer: Microsoft Outlook 14.0
    Thread-Index: AQHGFoMDkGWQh9QAPaZBgFNKO562rQIkqmV+AcwaFBeh2wbeEA==
    Content-Language: en-us
    X-AntiAbuse: This header was added to track abuse, please include it with
     any abuse report
    X-AntiAbuse: Primary Hostname - es26.siteground.eu
    X-AntiAbuse: Original Domain - xxxx.com
    X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
    X-AntiAbuse: Sender Address Domain - grand-eng.com
    X-Get-Message-Sender-Via: es26.siteground.eu: none
    X-Originating-IP: 77.104.147.176
    X-SpamExperts-Domain: es26.siteground.eu
    X-SpamExperts-Username: 77.104.147.176
    Authentication-Results: mailspamprotection.com; auth=pass
     smtp.auth=77.104.147.176@es26.siteground.eu
    X-SpamExperts-Outgoing-Class: ham
    X-SpamExperts-Outgoing-Evidence: Combined (0.02)
    X-Recommended-Action: accept
    X-Filter-ID: s0sct1PQhAABKnZB5plbIWJcQl9ohNb4q4dlucivUJP+Q5dV+Acsdi+yk//P2z2oiwQzKw+6v3Ca
     IMG6s7LqJPBvNpiZ5/Q3Hs04cb5YWj73RkO83TnZt5TkjsEinPqI3D5sBXSj6IrhaxFIitvoPCqU
     u1B+MaTJMNEfuhU6ffI61YsX2RGt1nU/xRjVCzeItfcbrK6AT77RRhdVH33wjhkT4hGdrV0PGMTr
     aEhJ4BR1ya1NxZI4oPlEBJXODbuKXNfQS/U6eCLjNy3Dxu8o4O5umWduIPIExSIS9Rm4+dW2bAMN
     ktw2lGWNwI0Vzs38bNNSq7msQerNGiO5li8RaoJ6NV63B1aAbzeGigS9RtafVsst/QEVbupaaYfx
     KYRJ6bYY5F2tlPERmvk3n2C4zt1ZJudBdXNxIh3O9fcMgBfJEP3apgZGCgFqkcVVxiqpJirJCJ11
     kNOYD+0zU2xKFt63fF/vjpfNqvGFL6g78KFsxlDO97EQIrfsioY0SHOXPBfyCUQPGRfAuQJyQcUh
     Q/OW6bvL9DC431WlF1LxckzntFx0g7g5LTQ00DHEknMDQTeOco22CwW4zctDdpQTFF8tUf5AMDZa
     Su6DF4GQNipnrqWGHcz5u2H0Q2lCzlNpLCrp+LJypxjJ2gnZjUaxIsguknaFDANL6ksLAMxuhq1z
     HDeqqFz43py4SDhdaHkWPLXDcrCIHDeANqFy8Kd34M4ACdbEKiS9G2PSp7ehuYuz423CBT0w+MM3
     ue0hYhwGQGAMjNHCJ/gW+K01tl4pU/22OmQ4eg7FnYUaGXSnlTht/RtYrSMXrCVO805tnHNq6FF+
     w+6c14cdVDYKgv7m8v347VwnBKiL9IiS4qwra4lkQKQkh2cSkcY9pfAbiOoL8hq6aNt+dDxkRvzn
     MHxhCQ==
    X-Report-Abuse-To: spam@quarantine1.mailspamprotection.com
    Return-Path: wail@grand-eng.com

    Wednesday, May 3, 2017 7:59 AM
  • Apologies for the overload of info,  but just trying to throw everything out there!

    One the hub transport receive connector servers seems to be throwing lots of critical error, sometimes leading to restarts. Attached is a screenshot showing these, with the error I think 'could' be relevant here highlighted. 

    Wednesday, May 3, 2017 11:18 AM