From: shahinaglobal@server.egclick.com (shahinaglobal at server.egclick.com)
To: linux-arm-kernel@lists.infradead.org
Subject: New status of your UPS delivery (code: 01870412)
Date: Sun, 30 Jul 2017 05:37:19 +0000 [thread overview]
Message-ID: <E1dbgul-0000jD-VW@server.egclick.com> (raw)
Dear Customer,
Your parcel was successfully delivered July 26 to UPS Station, but our courier cound not contact you.
You can find more details in this e-mail attachment!
Thank you for your time,
Wallace Lawson,
UPS Office Clerk.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: UPS-Package-01870412.zip
Type: application/zip
Size: 1175 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170730/469b19cd/attachment.zip>
reply other threads:[~2017-07-30 5:37 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=E1dbgul-0000jD-VW@server.egclick.com \
--to=shahinaglobal@server.egclick.com \
--cc=linux-arm-kernel@lists.infradead.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).