From: "Vivint Home Security" <vivint-home-security@averyandcompany.com>
To: <gdb-patches@sourceware.org>
Subject: Your Vivint.SmartHome Monitoring offer has arrived
Date: Tue, 24 Apr 2018 12:44:00 -0000 [thread overview]
Message-ID: <0.0.0.86.1D3DBC736ABF14A.5C7242@mail.averyandcompany.com> (raw)
Your Vivint.SmartHome Monitoring offer has arrived
http://www.averyandcompany.com/c9b6yZz2385J8A6G17kT121nv50nOC25d5L27AZHF-tDxGaIwfws4vGI6DvIEsvZ7NFTY13m6QkihWT/hand-class
Update Preferences- http://www.averyandcompany.com/5396jl23l85W86iN17X1B2152KN_JP25d5B27KZHF-tDxGaIwfws4vGI6DvIEsvZ6K13IBF6zNihj0/sentence-set
next reply other threads:[~2018-04-24 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 12:44 Vivint Home Security [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-01 12:23 Vivint Smart Home
2018-05-30 14:01 VIVINTPremierProvider
2018-04-30 11:26 Vivint USA
2018-04-27 11:47 Vivint USA
2018-04-03 12:33 Vivint USA
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=0.0.0.86.1D3DBC736ABF14A.5C7242@mail.averyandcompany.com \
--to=vivint-home-security@averyandcompany.com \
--cc=gdb-patches@sourceware.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).