Email delay for only one domain
Hopefully you can guide me if it is a problem in the server, in the network, or it is external.
Some emails are received with excessive delay. There are Banks emails that delay in arriving.
Red colour specify the time when i received mail in my server and the blue shows when mail delivered from destination server:
Mail header is given below (any idea?) :
Return-Path: <bblc.someusr@example.com>
Received: from whm.example.net
by whm.example.net with LMTP id gPG6Hh0BJFyKJgAALYpEHQ
; Thu, 27 Dec 2018 04:30:53 +0600
Return-path: <bblc.someusr@example.com>
Envelope-to: someusr2@example.com
Delivery-date: Thu, 27 Dec 2018 04:30:53 +0600
Received: from mail.example.com ([103.228.xxx.xxx]:37862)
by whm.example.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.91)
(envelope-from <bblc.someusr@example.com>)
id 1gcHhP-0002XV-Jw
for someusr2@example.com; Thu, 27 Dec 2018 04:30:53 +0600
Received: from mail.example.com (unknown [10.180.xx.xx]) by Email.domain.tld with smtp
id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969;
Thu, 27 Dec 2018 04:30:43 +0600
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.example.com (Postfix) with ESMTP id 4CB42287A2F;
Wed, 26 Dec 2018 14:55:00 +0600 (BDT)
X-Virus-Scanned: amavisd-new at
Received: from mail.example.com ([127.0.0.1])
by localhost (mail.example.com [127.0.0.1]) (amavisd-new, port 10026)
with ESMTP id K3D1GBzvmQ5B; Wed, 26 Dec 2018 14:55:00 +0600 (BDT)
Received: from IBBL14559 (unknown [10.192.xxx.xx])
by mail.example.com (Postfix) with ESMTPS id 2F5682877C8;
Wed, 26 Dec 2018 14:54:58 +0600 (BDT)
Received: from IBBL14559 (unknown [10.192.xxx.xx]) by Email.domain.tld with smtp
id 2915_da3f_f7726d36_b67d_4536_a454_fdc28c19f8b5;
Wed, 26 Dec 2018 14:54:57 +0600
Message-ID:
From: "someusr." <bblc.someusr@example.com>
To:
Subject:
Date: Wed, 26 Dec 2018 14:54:49 +0600
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0009_01D49D2A.F3631050"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.23651
X-NAI-Spam-Report: 1 Rules triggered
* -5000 -- WHITELISTED
X-NAI-Spam-Version: 2.3.0.9418 : core <6447> : inlines <6990> : streams
<1808285> : uri <2770492>
X-Spam-Status: No, score=-92.6
X-Spam-Score: -925
X-Spam-Bar: ---------------------------------------------------
X-Ham-Report: Spam detection software, running on the system "whm. example.net",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
root\@localhost for details.
Content preview: [...]
Content analysis details: (-92.6 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-100 USER_IN_WHITELIST From: address is in the user's white-list
4.2 BAYES_80 BODY: Bayes spam probability is 80 to 95%
[score: 0.8386]
-0.0 SPF_PASS SPF: sender matches SPF record
0.4 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
0.0 HTML_MESSAGE BODY: HTML included in message
1.8 PYZOR_CHECK Listed in Pyzor (Welcome to Pyzor"s documentation! " Pyzor 1.0 documentation')
1.0 KAM_HTMLNOISE Spam containing useless HTML padding
0.0 FSL_BULK_SIG Bulk signature with no Unsubscribe
X-Spam-Flag: NO
-
Could you also run the following and provide the output? exigrep 1gcHhP-0002XV-Jw /var/log/exim_mainlog
make sure to remove any identifying information such as domains/IP's as well. Thanks!0 -
It's a little hard to read through these headers. This message appears to be passing through a lot of different servers (or maybe daemons within the same physical server). The more "stuff" a message has to pass through, the more "areas" where you can have potential problems. In this particular case, the message got to: Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.example.com (Postfix) with ESMTP id 4CB42287A2F; Wed, 26 Dec 2018 14:55:00 +0600 (BDT) Relatively quickly. But then it took forever for the message to get to the next step: Received: from mail.example.com (unknown [10.180.xx.xx]) by Email.domain.tld with smtp id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969; Thu, 27 Dec 2018 04:30:43 +0600 About 13hrs 35mins What held the message up at the stop before (ESMTP id 4CB42287A2F)? That's not a cPanel server, because that's a Postfix ID. The next server is also not a cPanel server (id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969 ... I don't know what MTA uses this id syntax). But that would need to be your investigation point. What held the message up at that point? This assumes the time is correct on all servers. 0 -
It's a little hard to read through these headers. This message appears to be passing through a lot of different servers (or maybe daemons within the same physical server). The more "stuff" a message has to pass through, the more "areas" where you can have potential problems. In this particular case, the message got to: Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.example.com (Postfix) with ESMTP id 4CB42287A2F; Wed, 26 Dec 2018 14:55:00 +0600 (BDT) Relatively quickly. But then it took forever for the message to get to the next step: Received: from mail.example.com (unknown [10.180.xx.xx]) by Email.domain.tld with smtp id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969; Thu, 27 Dec 2018 04:30:43 +0600 About 13hrs 35mins What held the message up at the stop before (ESMTP id 4CB42287A2F)? That's not a cPanel server, because that's a Postfix ID. The next server is also not a cPanel server (id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969 ... I don't know what MTA uses this id syntax). But that would need to be your investigation point. What held the message up at that point? This assumes the time is correct on all servers.
@sparek-3 That is also my question!! My cPanel received mail on time --- Received: from mail.example.com (unknown [10.180.xx.xx]) by Email.domain.tld with smtp id 728a_00f7_6935b304_df40_4661_a4dd_c491711cb969; Thu, 27 Dec 2018 04:30:43 +0600 But unfortunately others domain received mail Wed, 26 Dec 2018 14:55:00 +0600 (BDT)........that is really unfortunate. And issue issue occurs from destination server, that have no access from my end. Blank on this point.0 -
So to clarify here, the delay is occurring on the remote/destination server, not yours? Once mail leaves your server enroute to it's destination delays aren't something you have any control over. 0 -
So to clarify here, the delay is occurring on the remote/destination server, not yours? Once mail leaves your server enroute to it's destination delays aren't something you have any control over.
Right you are.Communicating with remote server administrator. Thanks for your prompt reply.0
Please sign in to leave a comment.
Comments
7 comments