From: Jennifer Clark <jennifer.clark@technotradedata.com>
To: "mauve-discuss@sourceware.org" <mauve-discuss@sourceware.org>
Subject: Who's Next 2022 - Client Contact Details
Date: Wed, 28 Sep 2022 08:53:33 +0000 [thread overview]
Message-ID: <PNZPR01MB85232B340145F58D89CCB0C796549@PNZPR01MB8523.INDPRD01.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
Hi,
I hope you are doing great.
We are pleased to inform you that the business contacts from WHO' NEXT 2022 is available for purchase.
Please let me know if you are interested. So, that will get back to you with the Counts, Cost and other details ASAP.
Awaiting your response!
Kind Regards,
Jennifer Clark
Marketing executive
reply other threads:[~2022-09-28 8:53 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=PNZPR01MB85232B340145F58D89CCB0C796549@PNZPR01MB8523.INDPRD01.PROD.OUTLOOK.COM \
--to=jennifer.clark@technotradedata.com \
--cc=mauve-discuss@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).