Interestingly I’ve had this reported to me today as well.
There was a message from the beginning of the month about this but I was
away and don’t think anyone picked it up.
In all cases, the message is a message that has been greylisted
according to the logs yet it has been delivered to the recipient.
Here’s an example:
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> [SMTP Reply] 250 OK
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> adding new triplet:
(89.253.223.0,josep...@lakomvent.ru,recipi...@domain.tld) on host
my.servername.tld
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> to: recipi...@domain.tld recipient delaying
queued: recipi...@domain.tld
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> to: recipi...@domain.tld [SMTP Reply] 250 Accepted
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> to: recipi...@domain.tld recipient delayed:
recipi...@domain.tld
2017-07-18 22:20:23 m1-12823-00551 [Worker_3] [TLS-in] 89.253.223.149
<josep...@lakomvent.ru> to: recipi...@domain.tld [SMTP Status] 451 4.7.1
Greylisting, Please try again after 1 minute
Received message headers:
Received: from server.recipient.tld (1.1.1.1) by
server.recipient.tld (1.1.1.1) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.1.845.34
via Mailbox Transport; Tue, 18 Jul 2017 22:25:37 +0100
Received: from server.recipient.tld (1.1.1.1) by
server.recipient.tld (1.1.1.1) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.1.845.34; Tue, 18 Jul 2017 22:25:37 +0100
Received: from my.server.name (2.2.2.2 ) by
server.recipient.tld (1.1.1.1) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.1.845.34
via Frontend Transport; Tue, 18 Jul 2017 22:25:36 +0100
Received: from [127.0.0.1] (helo=vps-1033709-9570.host4g.ru)
by my.server.name with esmtp (Exim 4.86_2)
(envelope-from <josep...@lakomvent.ru>)
id 1dXa0l-00031j-1Q
for recipi...@domain.tld; Tue, 18 Jul 2017 22:26:34 +0100
Received: from vps-1033709-9570.host4g.ru ([89.253.223.149]
helo=vps-1033709-9570.host4g.ru)
by my.server.name with SMTPS(TLSv1_2
ECDHE-RSA-AES128-GCM-SHA256) (2.5.6); 18 Jul 2017 22:26:30 +0100
Received: by vps-1033709-9570.host4g.ru (Postfix, from userid 48)
id 88D4B2029E6F; Wed, 19 Jul 2017 00:20:20 +0300 (MSK)
From: Joseph C. <josep...@lakomvent.ru>
To: Recipient Name <recipi...@domain.tld>
Subject: [ Possibly Spam ] Enjoy your life, let's program works!
Thread-Topic: [ Possibly Spam ] Enjoy your life, let's program works!
Thread-Index: AQHTAAxl0AYbou0ktEiU2mMiTdVDrw==
Date: Tue, 18 Jul 2017 21:20:20 +0000
Message-ID: <8b391e9f77fb7215610f423dcbce0...@lakomvent.ru>
Content-Language: en-GB
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-AuthSource: server.recipient.tld
X-MS-Has-Attach:
X-MS-Exchange-Organization-Network-Message-Id:
76a6f9b5-1c7b-4506-cc1a-08d4ce23882f
X-MS-TNEF-Correlator:
x-assp-envelope-from: josep...@lakomvent.ru
x-assp-intended-for: recipi...@domain.tld
x-php-originating-script: 48:ewocuqmz.php(1166) : runtime-created
function(1)
: eval()'d code(1) : eval()'d code
x-spam-status: yes
x-mailer: PHPMailer 5.2.23 (https://github.com/PHPMailer/PHPMailer)
Content-Type: multipart/alternative;
boundary="_000_8b391e9f77fb7215610f423dcbce06aalakomventru_"
MIME-Version: 1.0
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
