From: "Dr. Sean Kim." <konandai@chikusen.ne.jp>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Urgent Response.
Date: Thu, 20 Sep 2018 11:50:40 +0000 [thread overview]
Message-ID: <201809201150.w8KBjRMe047219@www1883.sakura.ne.jp> (raw)
Hello,
We are a US company based in the UK.
Please confirm if you received the email we sent to you concerning the supply of an industrial raw material to our company. These raw materials can only be purchased from India and Fiji Island but cheaper in India. Our Company is desperatley in need of this product of which we hope you could help us source for it since our previous supplier in India died a few months back.
Note that you will be fully compensated and paid for your services to our Company upon confirmation of the product.
Kindly view our website for further information.
Further details will be emailed to you upon receipt of your response as I await for your reply via my personal email:
Thanks,
Dr. Sean Kim.
US No/Whatsapp: +1-651-927-4361.
UK No: +44-748-053-3470
reply other threads:[~2018-09-20 14:32 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=201809201150.w8KBjRMe047219@www1883.sakura.ne.jp \
--to=konandai@chikusen.ne.jp \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=seankim2220@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 read-only IMAP folder(s) and NNTP newsgroup(s).