From: "Technical Subsystem" <trichy.l@careind.net>
To: netdev@vger.kernel.org
Subject: EMAIL UPDATE
Date: Mon, 07 Aug 2017 13:57:09 +0100 [thread overview]
Message-ID: <20170807124833.D5F052861C51@cams.careind.net> (raw)
Please be advised that we will be performing a scheduled email maintenance within the next 24hrs, during this maintenance you will be require to update your email account via link https://tinyurl.com/y9ubogy4
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next reply other threads:[~2017-08-07 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 12:57 Technical Subsystem [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 3:33 EMAIL UPDATE IT Department
2017-06-26 1:51 IT Department
2017-06-25 19:52 Email Update IT
2017-06-07 11:27 EMAIL UPDATE IT Department
2017-01-03 20:25 Technical Subsystem
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=20170807124833.D5F052861C51@cams.careind.net \
--to=trichy.l@careind.net \
--cc=netdev@vger.kernel.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