How to monitor email deliverability?

Question

Email

The situation is this: there is an Exchange 2010 mail server and there is a [email protected] mailbox on it, there is also an external mailbox, for example, [email protected] The
task is to somehow monitor the letter sent to [email protected] from the mailbox [email protected] (and back), and in particular, you need to get the time it took for this letter to reach the gmail.com server from my mail server (and preferably back)
The task should be performed, for example, with an interval of 1 time in 10 minutes and so way to provide me with a complete picture of the availability of the server for receiving / receiving (you need to get logs) and analytics of the speed of passage / delivery of the letter.
Please share your thoughts on this, is it possible to implement this and if so, how? Thank you all in advance for your response.

Answer 1

1) Does the ekschenzha have logs? are they sane? is it possible to parse them?
2) Send a test letter on the scheduler from the local ekschenzh to your own test box on the gmail, on the other scheduler, use the console mail client to check the time of arrival of the letter.
Screw all this to nagios or the like (kakti, zabbix, etc.)

Answer 2

What's stopping you from seeing the headers? There you can find not only the path of the letter between the hosts, but also the time. First yanked email from gmail:
Delivered-To: [email protected]
Received: by 10.220.34.205 with SMTP id m13csp113897vcd;
Mon, 30 Jul 2012 09:27:43 -0700 (PDT)
Received: by 10.112.103.130 with SMTP id fw2mr5553698lbb.107.1343665662728;
Mon, 30 Jul 2012 09:27:42 -0700 (PDT)
Return-Path: <[email protected]>
Received: from my.phpclub.info (my.phpclub.info. [79.137.227.42])
by mx.google.com with ESMTPS id sq3si13782787lab.17.2012.07.30.09.27.42
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, Jul 30, 2012 09:27:42 -0700 (PDT)
Received-SPF: pass (google.com: domain of [email protected] designates 79.137.227.42 as permitted sender) client-ip=79.137.227.42;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of [email protected] designates 79.137.227.42 as permitted sender) [email protected]
Received: from wwwrun by my.phpclub.info with local (Exim 4.71)
(envelope-from <[email protected]>)
id 1Svspv-0004ZU-3b
for [email protected]; Mon, 30 Jul 2012 20:28:51 +0400
Message-Id: <[email protected]>
To: alekciy <[email protected]>
Subject: =?utf-8?Q?=D0=9E=D1=82=D0=B2=D0=B5=D1=82=20=D0=B2=20?==?utf-8?Q?=D0 =BE=D1=82=D1=81=D0=BB=D0=B5=D0=B6=D0=B8=D0=B2=D0=B0=D0=B5=D0=BC=D0=BE=D0=B9 =20?= =?utf-8?Q?=D1=82=D0=B5=D0=BC=D0=B5:=20?= =?utf-8?Q?=D0=9F=D0=B0= D0=B3=D0=B8=D0=BD=D0=B0=D1=86=D0=B8=D1=8F=20?==?utf-8?Q?=D0=B8=20?==?utf -8?Q?=D0=BF=D1=80=D0=BE=D0=B8=D0=B7=D0=B2=D0=BE=D0=B4=D0=B8=D1=82=D0=B5= D0=BB=D1=8C=D0=BD=D0=BE=D1=81=D1=82=D1=8C=20?==?utf-8?Q?LIMIT=20=D0=BD=D0=B0 =20?= =?utf-8?Q?=D0=B1=D0=BE=D0=BB=D1=8C=D1=88=D0=B8=D1=85=20=D1=81=D0=BF =D0=B8=D1=81=D0=BA=D0=B0=D1=85.?=
X-PHP-Originating-Script: 1000:Sendmail.php
From: =?utf-8?Q?PHPClub=20- =20=D0=BA=D0=BB=D1=83=D0=B1=20?==
?utf-8?Q?=D1=80=D0=B0=D0=B7=D1=80=D0=B0 =D0=B1=D0=BE=D1=82=D1=87=D0=B8=D0=BA=D0=BE=D0=B2=20PHP?= <[email protected]>
Date:Mon, 30 Jul 2012 16:28:51 +0000
Content-Type: multipart/alternative;
boundary="=_522558b722c1cab84a58b6dfc0ffb690"
MIME-Version: 1.0
Sender: WWW daemon apache <[email protected]>

Answer 3

> And it's not very clear how to track the time of passage of a letter from the local
> host to the receiving server in the internet.
If there is no access to the recipient's server (to the logs or a specific mailbox), but there is none, then the answer is no way. It is impossible to know when the letter was delivered to the addressee.
But if we send a letter from our server, then from the logs you can at least find out that 1) the letter was delivered to an authorized server (or a refusal was received and the reason was indicated); 2) delivery time. But when it reaches the address on the internal network, it will not be possible to find out from the outside.

Answer 4

Read here and here . On the other hand, you will suddenly see that letters from you reach gmail not in a couple of minutes, but, say, in half an hour. What will you do?

Answer 5

There is such an idea: let's say there is an email client that writes open logs about the arrival / departure of a letter, i.e. the letter goes out into the world (the time of sending is fixed) and is taken from the server by pop3 (the time of arrival is fixed). a parser is written for such logs and the time difference is fixed. Only I don’t know such a mail client that writes logs in this form. Maybe someone will tell?