From: "Delivery Subsystem" <POSTMASTER@hyperdata.com.my>
To: <mauve-patches@sourceware.org>
Subject: Message Delivery Failure - WARM REGARDS
Date: Mon, 29 Nov 2021 14:57:33 +0800 [thread overview]
Message-ID: <BED33C23C48B44A6B62E009507729DC8.MAI@southgate.biz> (raw)
MailEnable: Message could not be delivered to some recipients.
The following recipient(s) could not be reached:
Recipient: [SMTP:clgan333@gmail.com]
Reason: 550-5.7.26 This message does not have authentication information or fails to
Recipient: [SMTP:tangch11@gmail.com]
Reason: 550-5.7.26 This message does not have authentication information or fails to
Message contents follow:
Received: with MailEnable Postoffice Connector; Mon, 29 Nov 2021 14:57:27 +0800
Received: from omr21.orchid.atmailcloud.com ([52.221.55.32]) by southgate.biz with
MailEnable ESMTP; Mon, 29 Nov 2021 14:57:26 +0800
Received: from MRR.i-0066f3ed2d459790c
by OMR.i-083ffcf07d9ea6dc6 with esmtps
(envelope-from <mauve-patches@sourceware.org>)
id 1mrabJ-0008R5-GC; Mon, 29 Nov 2021 14:57:21 +0800
Received: from CMR.i-0378b006b4445375e by MRR.i-0066f3ed2d459790c with esmtps
(envelope-from <mauve-patches@sourceware.org>)
id 1mrabI-0001q2-G9; Mon, 29 Nov 2021 14:57:20 +0800
Received: from [203.125.107.34] (helo=DCRBCJ23.shengsheng.local)
by CMR.i-0378b006b4445375e with esmtp
(envelope-from <mauve-patches@sourceware.org>)
id 1mraZv-000351-48; Mon, 29 Nov 2021 14:55:59 +0800
Content-Type: multipart/alternative; boundary="===============1743420567=="
MIME-Version: 1.0
Subject: WARM REGARDS
To: Recipients <mauve-patches@sourceware.org>
From: "BEN JOHNSON" <mauve-patches@sourceware.org>
Date: Mon, 29 Nov 2021 14:52:11 +0800
Reply-To: bjattorneys5@gmail.com
X-Atmail-Id: mauve-patches@sourceware.org
X-atmailcloud-spam-score: 1000
X-atmailcloud-spam-bar: +++++++++++++++++++++++++++++++++++++++++++++++++++
X-atmailcloud-spam-action: reject
Message-ID: <91E414D056A840E18A2C04EC966A031C.MAI@southgate.biz>
You will not see this in a MIME-aware mail reader.
--===============1743420567==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Description: Mail message body
Good Day,
An exhaustive and meticulous search was conducted and it is in connection =
with this search that I'm writing to you today base on your surname which y=
ou share with a client that is now deceased. Revert back to me for more det=
ails to be given to you. =
Sincerely,
Barr Ben Johnson
--===============1743420567==
Content-Type: text/html; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Description: Mail message body
<HTML><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Diso-8859-1"/></head><BODY><P>Good Day,</P>
<P>An exhaustive and meticulous search was conducted and it is in connectio=
n with this search that I'm writing to you today base on your surname which=
you share with a client that is now deceased. Revert back to me for more d=
etails to be given to you. </P>
<P>Sincerely,<BR>Barr Ben Johnson</P></BODY></HTML>
--===============1743420567==--
reply other threads:[~2021-11-29 6:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BED33C23C48B44A6B62E009507729DC8.MAI@southgate.biz \
--to=postmaster@hyperdata.com.my \
--cc=mauve-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).