From: "noreply@capcommunity.co.za" <noreply@capcommunity.co.za>
To: "mauve-patches@sourceware.org" <mauve-patches@sourceware.org>
Subject: Technical: 00020941 - WARM REGARDS
Date: Mon, 29 Nov 2021 06:51:21 +0000 (GMT) [thread overview]
Message-ID: <mR0KV000000000000000000000000000000000000000000000R3BN1L009_BP1yv6QYmehw6HWdg4ug@sfdc.net> (raw)
Hi ,
Thank you for your email.
A CAP Security Systems representative will be allocated to this ticket and will be in touch within one working day. We strive to resolve all issues in the shortest possible time.
Please see below the case details:
Case number: 00020941
Case subject: WARM REGARDS
Case status: Open
Regards
The CAP Security Systems Team
reply other threads:[~2021-11-29 6:51 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=mR0KV000000000000000000000000000000000000000000000R3BN1L009_BP1yv6QYmehw6HWdg4ug@sfdc.net \
--to=noreply@capcommunity.co.za \
--cc=mauve-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).