From: Stephen Li <stenn6-Fho7fi8YkfY@public.gmane.org>
To: unlisted-recipients:; (no To-header on input)
Subject: REF
Date: Tue, 17 Mar 2020 12:09:27 +0000 (UTC) [thread overview]
Message-ID: <1348826789.1834294.1584446967790__2633.00494277559$1584447099$gmane$org@mail.yahoo.com> (raw)
In-Reply-To: 1348826789.1834294.1584446967790.ref@mail.yahoo.com
Greetings,
I was searching through a local business directory when I found your
profile. I am Soliciting On-Behalf of my private client who is
interested in having a serious business investment in your country. If
you have a valid business, investment or project he can invest
back to me for more details. Your swift response is highly needed.
Sincerely
Stephen Li
Please response back to me with is my private email below for more details
stephli947701-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
parent reply other threads:[~2020-03-17 12:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1348826789.1834294.1584446967790.ref@mail.yahoo.com>]
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='1348826789.1834294.1584446967790__2633.00494277559$1584447099$gmane$org@mail.yahoo.com' \
--to=stenn6-fho7fi8ykfy@public.gmane.org \
--cc=stephli947701-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 NNTP newsgroup(s).