From: "Laura Prickett" <laura.b2bexpoattendees@gmail.com>
To: <gcc@gcc.gnu.org>
Subject: Energy Exchange 2022 Attendees
Date: Wed, 14 Dec 2022 09:42:26 -0500 [thread overview]
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAP4qlhNnohBHme/DiIPepuTCgAAAEAAAAN9pm23y/wtLhhv8lrAHiiEBAAAAAA==@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi,
Would you be interested in obtaining the Energy Exchange 2022 attendance
database?
Facility managers, Fleet managers, Water managers, State resource managers,
City planners, Procurement officers, Building commissioners, Project
implementation specialists, Energy auditors, Compliance managers, financial
managers, Attorneys, Engineers, and more are among the attendees.
Please express your thoughts with me so that I can provide you more detailed
information.
Sincere regards,
Laura Prickett | Associate for Business Development
Note: You were specifically sent this email based upon your company profile.
If you do not wish to hear from you further, please reply with "REMOVE".
reply other threads:[~2022-12-14 14:43 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=''\!'&'\!'AAAAAAAAAAAYAAAAAAAAAP4qlhNnohBHme/DiIPepuTCgAAAEAAAAN9pm23y/wtLhhv8lrAHiiEBAAAAAA==@gmail.com' \
--to=laura.b2bexpoattendees@gmail.com \
--cc=gcc@gcc.gnu.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).