Issue Certain emails are received with delay

[Ihtshama]

Hi,
one of my client complained that for certain domains, he is recieveing emails after 10-20 min delay. Today i experienced the same thing. I was not able to recieve email until 15 min. During this time, other emails were being recieved normally.

Is there anything missing or problem with this?

 

[Monty]

First thing to do: Check the headers of one of the delayed mails. There you'll see the "Received" lines (starting from the bottom going up). Each line contains a timestamp so you can see where the delay occurred.

If the delay happened between the last remote server and your server: Check your postfix logfiles around the time of the mail delivery for any entries that explain the delay. Maybe your server was temporarily rejecting the incoming mail with a 4xx error code. You will get an error message that explains why the mail was delayed.

To understand how to read mail headers, have a look here: How to Read and Analyze the Email Header Fields and Information about SPF, DKIM, SpamAssassin

 

[Ihtshama]

Hi
thank you for your reply. I can see where is the delay, i believe it was kept by the mandril app on the sender side, NO?
Please check out as highlighted in red.

thank you in advance for your help.


X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
mail.professionaldesigner.ch
X-Spam-Level:
X-Spam-Status: No, score=-1.5 required=7.0 tests=BAYES_00,HTML_MESSAGE,
MIME_HTML_MOSTLY,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID,
T_REMOTE_IMAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1
Received: (qmail 19501 invoked from network); 19 May 2018 13:46:34 +0200
Authentication-Results: mail.professionaldesigner.ch;
dmarc=none (p=NONE sp=NONE) d=mandrillapp.com; header.from=yunojuno.com;
dkim=pass header.i=bounce-md_30898983.5b000b11.v1-82ffb9e7b21f4a2c8fc9680a9b321341@mandrillapp.com;
spf=pass (sender IP is 198.2.133.11) smtp.mailfrom=bounce-md_30898983.5b000b11.v1-82ffb9e7b21f4a2c8fc9680a9b321341@mandrillapp.com smtp.helo=mail133-11.atl131.mandrillapp.com
Received-SPF: pass (mail.professionaldesigner.ch: domain of mandrillapp.com designates 198.2.133.11 as permitted sender) client-ip=198.2.133.11; envelope-from=bounce-md_30898983.5b000b11.v1-82ffb9e7b21f4a2c8fc9680a9b321341@mandrillapp.com; helo=mail133-11.atl131.mandrillapp.com;
Received: from mail133-11.atl131.mandrillapp.com (198.2.133.11)
by mail.professionaldesigner.ch with (DHE-RSA-AES256-GCM-SHA384 encrypted) SMTP; 19 May 2018 13:46:33 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=mandrill; d=yunojuno.com;
h=From:Subject:Reply-To:Message-Id:Toate:MIME-Version:Content-Type; [email protected];
bh=EU5cO4t1dvwtAuUrcaorCzOrtOFGs0WbOTxpFXEFuHs=;
b=gjxf1R3WdMRMq8QP0UCMacMM6CnSzU48cQz12ta4tf4XKG0XSXzGwjA5fxXpyNuG/OzkGq5KLpHN
hLP8JiLEizeqk1NictBljsWsxf/xd/AOvvm5okEhnUDhRHxZvxnc5aouXj06uYPt0kuwAxznXg0c
ubnng4ZwtqAqef1wINA=
Received: from pmta02.mandrill.prod.atl01.rsglab.com (127.0.0.1) by mail133-11.atl131.mandrillapp.com id h0079i1sar89 for <[email protected]>; Sat, 19 May 2018 11:31:30 +0000 (envelope-from <bounce-md_30898983.5b000b11.v1-82ffb9e7b21f4a2c8fc9680a9b321341@mandrillapp.com>)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com;
[email protected]; q=dns/txt; s=mandrill; t=1526729489; h=From :
Subject : Reply-To : Message-Id : To : Date : MIME-Version :
Content-Type : From : Subject : Date : X-Mandrill-User :
List-Unsubscribe; bh=EU5cO4t1dvwtAuUrcaorCzOrtOFGs0WbOTxpFXEFuHs=;
b=SNGA+mM/J+rACuQSI8EfMSFBeVJXoa+Ut2Ex80WAWHry6Qdk24GQI0oqBhY8srEw/OFF3R
Vx0Lya7dS3p1jovXXLe9KmnBy1IhT2VVrbflZrd8S0jGMgvkzflKEG/Wt7XMMhNIaTOHwqAU
7VZXm7lIt2tJoP+4z/Y/DkIZAdoDk=
From: YunoJuno-bot <[email protected]>
Subject: =?utf-8?Q?We=E2=80=99ll=20be=20with=20you=20soon?=
Return-Path: <bounce-md_30898983.5b000b11.v1-82ffb9e7b21f4a2c8fc9680a9b321341@mandrillapp.com>
Received: from [54.217.148.63] by mandrillapp.com id 82ffb9e7b21f4a2c8fc9680a9b321341; Sat, 19 May 2018 11:31:29 +0000
X-Appmail-Template: name=agency_registration_city_not_live; language=en-gb; version=2
Reply-To: <[email protected]>
Message-Id: <20180519113129.55.19644@f36741bb-6624-4c0a-97b1-2af4e290a24c.prvt.dyno.rt.heroku.com>
To: <[email protected]>
X-Report-Abuse: Please forward a copy of this message, including all headers, to [email protected]
X-Report-Abuse: You can also report abuse here: Abuse | Mandrill
X-Mandrill-User: md_30898983
Date: Sat, 19 May 2018 11:31:29 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_av-tUkBTDJE1DupFdXpCWSaSg"

 

[Monty]

The delay was between 198.2.133.11 (the sender MTA) and your server. Please check your postfix logs and search for entries containing "198.2.133.11" between 13:31 and 13:46.
Maybe 198.2.133.11 tried to connect to your server at 13:31 but received a 4xx temporary error, so it tried again 15 minutes later and succeeded.
Do you have greylisting enabled on your server?

 

[Ihtshama]

Yes, Switch on server-wide greylisting spam protection is ON

I am struggling to access that logs. I remember, in old PC, i used to have a small software similar to Putty, where i can access ubuntu file system using GUI, i forgot its name, any idea please? i am not good at linux at all.

 

[Monty]

Yes, Switch on server-wide greylisting spam protection is ON

I am struggling to access that logs. I remember, in old PC, i used to have a small software similar to Putty, where i can access ubuntu file system using GUI, i forgot its name, any idea please? i am not good at linux at all.

You can access your server with SSH, if you are the admin of the server and you have root access. For this you'll need an SSH client such as PuTTY, you can download that for free.
The postfix log file is called /var/log/mail.log (on Ubuntu/Debian systems) or /var/log/maillog (on Redhat/CentOS systems). You can read this log file using a file viewer such as "less" or an editor such as vi/vim, joe etc. Maybe you check with somebody you know and is more used to working with the Linux shell for help.

You may want to consider whitelisting some sender domains in case you have recurring delays with mails from those domains. More info about Plesk greylisting configuration can be found here: How to configure Greylisting