From: "Steve Timber via ecos-discuss" <ecos-discuss@ecos.sourceware.org>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] NRF Expo
Date: Mon, 17 Dec 2018 18:27:00 -0000 [thread overview]
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAMlIZU7wBcNEusNuLh6+GwDCgAAAEAAAAHdOqF8qhfRJoioZsRy5CUkBAAAAAA==@expodatapro.com> (raw)
Hi,
I am following up to check if your company is interested in acquiring
Attendees List of NRF Expo 2019?
Expo Details:
Date: 13 - 15 January
Location: New York, NY
Expo Name: NRF Expo 2019.
Total Attendees Count: 35,000 Attendees
Data Fields includes: Company name, Contact name, Title, Email address,
Website, Telephone number.
Please let me know your thoughts and I shall get back to you with the
Pricing.
Awaiting your reply
Thanks & Regards,
Steve Timber
Lead Generation Executive
To opt out, please reply with "Leave Out" in the Subject Line.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2018-12-17 18:27 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=''\!'&'\!'AAAAAAAAAAAYAAAAAAAAAMlIZU7wBcNEusNuLh6+GwDCgAAAEAAAAHdOqF8qhfRJoioZsRy5CUkBAAAAAA==@expodatapro.com' \
--to=ecos-discuss@ecos.sourceware.org \
--cc=steve.timber@expodatapro.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).