From: "Alison B Ortiz" <stevewinwiood@65-114-47-43.dia.static.qwest.net>
To: ashleykeesis@windsorbeacon.com
Cc: karigalasso@gmail.com, geis3@msn.cn, amohan1@binghamton.edu,
linux-arch@vger.kernel.org, sjg@sun0.melb.bull.oz.au,
jmcho@nlprep.sogang.ac.kr, sarah.fox@cancer.org,
-staff@kent.ac.uk, clark@clarkequipment.com
Subject: direct mail mailing lists
Date: 26 Apr 2010 22:29:28 -0400 [thread overview]
Message-ID: <SERVER3tJAadVe5HXC90000056c@server3> (raw)
Corrine,
Contact me at the email address below for a catalog of all our USA lists.
Also, this week we are offering reduced costs for more than one list.
Regards,
Lorrie Gabriel
Email Address: successtools@gmx.com
email for delisting
reply other threads:[~2010-04-27 4:22 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=SERVER3tJAadVe5HXC90000056c@server3 \
--to=stevewinwiood@65-114-47-43.dia.static.qwest.net \
--cc=-staff@kent.ac.uk \
--cc=amohan1@binghamton.edu \
--cc=ashleykeesis@windsorbeacon.com \
--cc=clark@clarkequipment.com \
--cc=geis3@msn.cn \
--cc=jmcho@nlprep.sogang.ac.kr \
--cc=karigalasso@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=sarah.fox@cancer.org \
--cc=sjg@sun0.melb.bull.oz.au \
/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).