[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 548
  • Last Modified:

Messages getting delayed from a single domain

We are currently having an issue with one of our clients we any messages they send to us get delayed by anything from 4 to 8 hours.

It is only this particular domain, all other messages are being received from all over the world without issue.

The client is adiment there is no problem there side as it is only our domain that they are experiencing problems with.

Any ideas?

Dan
0
afrikapr
Asked:
afrikapr
  • 4
  • 3
  • 3
  • +1
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Did you check the Header of the email and check where the delay is if its after it enters your environment it will tell you from which location to which location was the delay and we can work accordingly ......

If the delay is before it comes to your environment .... nothing can be done ..... then just need to check if the delay is on the recipient or where :)

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
If the issue is with one Domain .... i doubt Exchange or your environment will be Bias just to them :)

- Rancy
0
 
DLeaverCommented:
What do you use for your anti spam product?  

You may have greylisting enabled which is slowing this particular clients email down, if you have an anti spam product check there and check any logging.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Exchange_GeekCommented:
I think what Rancy mentioned is correct - one should start with basics and message header would clearly tell you that the delay is on your Exchange environment side OR the sender side. It is simple and should be the first step to troubleshoot such issues.

Once, it is determined that the issue is on your side, you'll need to refer to the server / appliance that held the message and work on it to determine the cause of it.

it may be AV, may be anti spam agent, may be just the server acting weird - hundreds of reasons - that we can work with to solve - but we should move step-by-step. Jumping to look at million of steps will not only confused us but would be waste of your time too, which we do not want at any cost.

Regards,
Exchange_Geek
0
 
DLeaverCommented:
Just putting an idea out there guys from seeing this before in the past

I agree though, checking the headers is the best place to start....
0
 
afrikaprAuthor Commented:
Thanks for the input guys.

We are using Forefront for Exchange, but the domain in question and IP address are clean on that, so dont believe that to be an issue.

Checking the internet headers appears to be delayed between their server & ours, example to internet header from delayed message below:

Received: from mail.selectharvests.com.au (203.58.22.34) by
 server.africaproductsl.co.uk (192.168.10.2) with Microsoft SMTP Server id
 8.1.393.1; Fri, 24 Aug 2012 16:48:44 +0100
Received: from MALABE.selectharvests.com.au ([::1]) by
 Malabe.selectharvests.com.au ([::1]) with mapi id 14.01.0323.003; Fri, 24 Aug
 2012 11:51:59 +1000
From: Phi Dang <pdang@selectharvests.com.au>
To: Loi <loi@africaproducts.co.uk>, Administration <info@africaproducts.co.uk>
CC: Laurence Van Driel <LVanDriel@selectharvests.com.au>, Peter Easdown
      <PEasdown@selectharvests.com.au>
Date: Fri, 24 Aug 2012 02:51:57 +0100
Subject: 230812X
Thread-Topic: 230812X
Thread-Index: Ac2Bmu3JAQy+Jwd9T9eto3VuJsW/Hw==
Message-ID:
 <19EFB2ACC32E9C4DB198A6E5863C6B935700A6@Malabe.selectharvests.com.au>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: SERVER.africaproductsl.local
X-MS-Has-Attach: yes
X-MS-Exchange-Organization-SenderIdResult: None
X-MS-Exchange-Organization-SCL: -1
X-MS-Exchange-Organization-PRD: selectharvests.com.au
X-MS-TNEF-Correlator:
acceptlanguage: en-AU, en-US
received-spf: None (SERVER.africaproductsl.local:
 pdang@selectharvests.com.au does not designate permitted sender hosts)
x-originating-ip: [192.168.1.182]
Content-Type: multipart/mixed;
      boundary="_002_19EFB2ACC32E9C4DB198A6E5863C6B935700A6Malabeselectharve_"
MIME-Version: 1.0

This message took over 13 hours to be received.

Any further thoughts wouild be greatly appreciated.

Dan
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Received: from mail.selectharvests.com.au (203.58.22.34) by
 server.africaproductsl.co.uk (192.168.10.2) with Microsoft SMTP Server id
 8.1.393.1; Fri, 24 Aug 2012 16:48:44 +0100
Received: from MALABE.selectharvests.com.au ([::1]) by
 Malabe.selectharvests.com.au ([::1]) with mapi id 14.01.0323.003; Fri, 24 Aug
 2012 11:51:59 +1000


The data is missing where we do not see handshake and email delivery happening between "Malabe.selectharvests.com.au" and "Microsoft SMTP Server".

- Rancy
0
 
afrikaprAuthor Commented:
Thanks for the further comment.

Have checked further and all messages, coming from that domain only contain the information above (or equivalent), even before this problem occurred .

Dan
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Then need to check with their ISP provider where the delay is happening as this does not gives a complete picture ?

If the issue is with one domain i cant think MS server has anything to do rather than some ISP :)

- Rancy
0
 
DLeaverCommented:
Just chucking some more thoughts out there...

Does this happen to a simple mail with no attachments?

Does the email contain any sort of signature or overly complex disclaimer?

Outside of that I agree with Rancy (again) in that the issue must lie in one of the relay servers between your company and the client.....the ISP should be able to help with this
0
 
Exchange_GeekCommented:
Received: from mail.selectharvests.com.au (203.58.22.34) by
 server.africaproductsl.co.uk (192.168.10.2) with Microsoft SMTP Server id
 8.1.393.1; Fri, 24 Aug 2012 16:48:44 +0100
Received: from MALABE.selectharvests.com.au ([::1]) by
 Malabe.selectharvests.com.au ([::1]) with mapi id 14.01.0323.003; Fri, 24 Aug
 2012 11:51:59 +1000

What should clear the picture is-
server.africaproductsl.co.uk - belongs to you OR sender?
MALABE.selectharvests.com.au - belongs to you OR sender?

Though i can guess the answer, but wouldn't want to assume stuff here.

Regards,
Exchange_Geek
0
 
afrikaprAuthor Commented:
server.africaproductsl.co.uk - belongs to us
MALABE.selectharvests.com.au - belongs to sender
0
 
Exchange_GeekCommented:
So, its clear that you're "server" got the email from "MALABE" after a long time. Not you're server fault, header shows clearly that "MALABE" was holding on to the email for reasons unknown to us and passed on the email to you late.

Get back to the sender and ask them to hunt their message logs and tell you whats wrong.

It cannot be more simpler than this.

Regards,
Exchange_Geek
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 4
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now