From: "Acct. Dept." <chukwudi@ego.net>
To: unlisted-recipients:; (no To-header on input)@mail.corp.redhat.com
Subject: STRICTLY CONFIDENTIAL
Date: Wed, 2 Nov 2016 19:23:13 -0500 [thread overview]
Message-ID: <201611022356.uA2NukHv012062@infonetg.com> (raw)
I have important transaction for you as next of kin to claim US$18.37m Mail me on my private email: chimwiakim@gmail.com
so I can send you more details
Thanks
Mr.Chim Wai Kim
======================================MOVE TO INBOX=======================
DISCLAIMER: This email and any files it contains are confidential and intended for the use of the recipient(s) only. If you are not the intended recipient you should notify the sender immediately and destroy the material from your system.
next reply other threads:[~2016-11-03 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 0:23 Acct. Dept. [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-18 3:22 STRICTLY CONFIDENTIAL Acct. Dept.
2016-11-20 7:50 Acct. Dept.
2016-09-09 18:24 Acct. Dept.
2016-05-07 6:22 Acct. Dept. Bank Of China
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=201611022356.uA2NukHv012062@infonetg.com \
--to=chukwudi@ego.net \
--cc=chimwiakim@gmail.com \
/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 NNTP newsgroup(s).