From: "Bernie Innocenti via RT" <sysadmin@gnu.org>
To: fche@redhat.com, gerald@pfeifer.com, ian@airs.com
Cc: overseers@gcc.gnu.org
Subject: [gnu.org #670482] SPF record for gcc.gnu.org
Date: Mon, 14 Feb 2011 23:30:00 -0000 [thread overview]
Message-ID: <rt-3.4.5-13863-1297726234-1063.670482-5-0@rt.gnu.org> (raw)
In-Reply-To: <rt-3.4.5-13863-1297719825-180.670482-5-0@rt.gnu.org>
> [ian@airs.com - Mon Feb 14 16:43:45 2011]:
> > gcc.gnu.org. TXT "v=spf1 a ?all"
> >
> > If you agree, I'll go ahead and make the change.
>
> OK, let's do that. Thanks.
Ok, done.
> I actually think it is very unwise for people to send e-mail using
> addresses @gcc.gnu.org. gcc.gnu.org hosts software development
> projects, and is absolutely not intended to serve as an e-mail
> forwarding address. However, I suppose we shouldn't break people doing
> that without any notice.
But then, why do we give @gcc.gnu.org aliases to all maintainers? I don't use mine these days, but I've always assumed it
was ok to use it for anything related to GCC development.
--
Bernie Innocenti
Systems Administrator, Free Software Foundation
next prev parent reply other threads:[~2011-02-14 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-670482@rt.gnu.org>
2011-02-14 16:43 ` Ian Lance Taylor
2011-02-14 16:58 ` Gerald Pfeifer
2011-02-14 17:01 ` Frank Ch. Eigler
2011-02-14 18:58 ` [gnu.org #670482] " Bernie Innocenti via RT
2011-02-14 21:43 ` Ian Lance Taylor
2011-02-14 21:43 ` ian@airs.com via RT
2011-02-14 23:30 ` Bernie Innocenti via RT [this message]
2011-02-15 1:20 ` Christopher Faylor
2011-02-15 1:20 ` Christopher Faylor via RT
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=rt-3.4.5-13863-1297726234-1063.670482-5-0@rt.gnu.org \
--to=sysadmin@gnu.org \
--cc=fche@redhat.com \
--cc=gerald@pfeifer.com \
--cc=ian@airs.com \
--cc=overseers@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).