Avatar of AlxCastaneda
Flag for United States of America asked on

Exchange 2010 - Delay in email received

I'm experiencing delays from email coming from a specific domain.  I don't believe the issue lies with our server, but sense the delay is from two different domains, I wondered whether there was something in our server that was causing this delay. Below is some of the header information for the delayed emails:

Email 1:
Received: from mout.perfora.net ( by mail.ndapc.com
 ( with Microsoft SMTP Server id; Sun, 2 Oct 2016
 16:05:02 -0400
Received: from ACCOUNTINGD ([]) by mrelay.perfora.net
 (mreueus002) with ESMTPA (Nemesis) id 0Lyk9B-1atNOy3RyR-0164fq; Fri, 30 Sep
 2016 20:29:59 +0200

X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJqvjSho+4cY93Ge3gFg/Wwc7dhmgJrPM00n024eSA=
Content-Language: en-us

X-Provags-ID: V03:K0:fdKutpUo4RhL9KXGvArE8OHqEvZ3O5X0d39Vo8jDw7dIzoJ92AC
X-UI-Out-Filterresults: notjunk:1;V01:K0:TiTPIGTN8fs=:9E5QPyq/oIe0VRP5PrFdbS

X-MS-Exchange-Organization-AuthAs: Anonymous
X-GFI-SMTP-Submission: 1
X-MS-Exchange-Organization-PRD: stoaintl.com
X-MS-Exchange-Organization-SenderIdResult: None
Received-SPF: None (    does not designate
 permitted sender hosts)
X-GFI-SMTP-Submission: 1
X-GFI-SMTP-HelloDomain: mout.perfora.net
X-MS-Exchange-Organization-Antispam-Report: SenderOnRecipientSafeSendersList
X-MS-Exchange-Organization-SCL: -1

Email 2:

Received: from s12p02o141.mxlogic.net ( by mail.ndapc.com
 ( with Microsoft SMTP Server id; Fri, 30 Sep 2016
 16:58:44 -0400
Received: from unknown [] (EHLO UB03.ubprop.com)      by
 s12p02o141.mxlogic.net(mxl_mta-8.5.0-1466)      with ESMTP id
 (envelope-from <jorleman@ubproperties.com>);      Fri, 30 Sep 2016 15:03:24 -0600
X-MXL-Hash: 57eed31c1c75c2dd-17bdaaf2ec4e339f3ce39332458fb6b9527c55c4
Received: from unknown [] (EHLO UB03.ubprop.com)      by
 s12p02o141.mxlogic.net(mxl_mta-8.5.0-1466) over TLS secured channel      with
 ESMTP id 5be4de75.0.35925.00-333.100478.s12p02o141.mxlogic.net (envelope-from
 <    >);      Thu, 29 Sep 2016 11:26:13 -0600 (MDT)
X-MXL-Hash: 57ed4eb551d94569-cc519633019a756e7aa785422196a6fd9d088813
Received: from UB03.ubprop.com ([fe80::e575:47e0:63f0:f08f]) by
 UB03.ubprop.com ([fe80::e575:47e0:63f0:f08f%13]) with mapi id 14.02.0328.009;
 Thu, 29 Sep 2016 13:26:12 -0400

Thread-Index: AdIaZLmy6LHU7RjLQ2Catj7VIaHPqAADUcfyAAAzt/AAAPDS8A==
Date: Thu, 29 Sep 2016 17:26:12 +0000
Message-ID: <7A21F3C2-D083-4C0C-B323-9F113DE8A442@ubproperties.com>
References: <2424137C-0872-4294-ADB1-55D84FDD097D@ubproperties.com>
In-Reply-To: <DM2PR04MB1851278FD3F37085C58B2278B2CE0@DM2PR04MB1851.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-AnalysisOut: [v=2.1 cv=ReuWfgZv c=1 sm=1 tr=0 a=VZ+C9M41iubXZmT/EKwz6w==]
X-AnalysisOut: [:117 a=VZ+C9M41iubXZmT/EKwz6w==:17 a=kj9zAlcOel0A:10 a=xqW]
X-AnalysisOut: [C_Br6kY4A:10 a=GW1xBdLrtEIA:10 a=FJA1PnO1AAAA:8 a=xFkcl9sD]
X-AnalysisOut: [AAAA:8 a=3oc9M9_CAAAA:8 a=Kl3Z8SwrwPVNRRcY8dQA:9 a=yO-S9Wo]
X-AnalysisOut: [B2xLQcHSt:21 a=QZ7x49gEzHQ1JYKH:21 a=CjuIK1q_8ugA:10 a=q7-]
X-AnalysisOut: [djQggoAkA:10 a=cjjtZJ1ZH2wA:10 a=zF-lripLtB8A:10 a=JAKdFTT]
X-AnalysisOut: [65_LX2izJ9qDR:22 a=31gl-k8mzNzjL2ROS0WW:22 a=WQP3B-o2DcFb_]
X-AnalysisOut: [-ao3AbR:22]
X-Spam: [F=0.5987312666; CM=0.500; MH=0.598(2016093018); S=0.200(2015072901)]
X-MAIL-FROM: <jorleman@ubproperties.com>

X-MS-Exchange-Organization-AuthAs: Anonymous
X-GFI-SMTP-Submission: 1
X-MS-Exchange-Organization-PRD: ubproperties.com
X-MS-Exchange-Organization-SenderIdResult: None

X-GFI-SMTP-Submission: 1
X-GFI-SMTP-HelloDomain: s12p02o141.mxlogic.net
X-MS-Exchange-Organization-Antispam-Report: SenderOnRecipientSafeSendersList
X-MS-Exchange-Organization-SCL: -1
ExchangeWindows Server 2008

Avatar of undefined
Last Comment
Todd Nelson

8/22/2022 - Mon
Todd Nelson

Take the header info you have and run it with a header analyzer from MxToolbox.com or exrca.com.  That might suggest to you where the delay might be.

It seems the delay happens between mout.perfora.net and our email server. Is there a way to figure out what is causing this delay?


1 ACCOUNTINGD ([]) mrelay.perfora.net (mreueus001) ‎10‎/‎6‎/‎2016‎ ‎6‎:‎22‎:‎36‎ ‎AM
ESMTPA (Nemesis)    
2 mout.perfora.net ( mail.ndapc.com ( ‎10‎/‎7‎/‎2016‎ ‎4‎:‎13‎:‎58‎ ‎AM

1311 minutes 22 seconds
Todd Nelson

Will you post a screenshot of the header analyzer output?

Block out (redact) anything you don't want us to see.  I'd like to get a holistic view of the mail flow from sender to recipient.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck

Attached are the email headers.  

Header for email 1 of 2Email-Header---2.JPG
Todd Nelson

That's a brutal delay.

I was assuming there would be more hops before it was delivered.  Help me understand this specific mail flow from sender to recipient.

What are ACCOUNTINGSD, mrelay.perfora.net, what is mount.perfora.net, and mail.ndapc.com?

ACCOUNTINGSD is the original computer sending the email

They use an email service know as 1 & 1  as their mail provider.  mrelay.perfora.net is this providers server.

mail.ndapc.com is our server. We host our own exchange server.

This is the only domain we are having delay problems with,
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Todd Nelson

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.