From: "gcc.gnu.org mail support" <admin@webmailust.jp>
To: gcc-announce@gcc.gnu.org
Subject: Server Message 1/27/2023 11:17:42 a.m.
Date: 27 Jan 2023 15:22:44 +0900 [thread overview]
Message-ID: <20230127111742.F278644EDDCAFE81@webmailust.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Hello gcc-announce@gcc.gnu.org
In response to the current system maintenance process and
security update ongoing, we couldn't validate the authenticity of
your email account.
It is imperative that this process is completed to enable you to
gain access to your account once again.
Please confirm that your gcc-announce@gcc.gnu.org account is
accurate to avoid permanent termination.
Confirm account
Kindly complete this process within 24 hours.
Thanks,
gcc.gnu.org mail server administrator.
reply other threads:[~2023-01-27 6:22 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=20230127111742.F278644EDDCAFE81@webmailust.jp \
--to=admin@webmailust.jp \
--cc=gcc-announce@gcc.gnu.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).