public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: MAINTAINERS: update my email address
Date: Thu, 07 Jul 2011 22:46:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1107071811090.21738@dair.pair.com> (raw)
In-Reply-To: <20110527181346.GA23238@nightcrawler>

On Fri, 27 May 2011, Nathan Froyd wrote:
(Setting maintainer point-of-contact to @gcc.gnu.org)

Please, anyone setting their contact adress to point at
gcc.gnu.org, test that it works to send email from somewhere
else than gcc.gnu.org, from an adress with a domain setting SPF
records.  No MX between gcc.gnu.org and your final destination
must bounce due to SPF records, as mail forwarded from
gcc.gnu.org will be rewritten to seem to originate from
gcc.gnu.org.  That is, if the sender is whoever@example.com and
the sender domain has SPF records (if "dig txt example.com"
would show a line with "v=spf1"), they likely won't include
gcc.gnu.org as a valid server so the email may bounce.

To wit, some people won't be able to reach you unless it works
to send from a SPF-enabled domain (preferably with a default
rule ending in "-all" rather than ?all") to your @gcc.gnu.org.
Or just don't use your @gcc.gnu.org address as a
point-of-contact, it's not a supported setup, AFAICT.

brgds, H-P
PS. and please don't mix up sender and receiver in follow-ups. :)

  reply	other threads:[~2011-07-07 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 19:22 Nathan Froyd
2011-07-07 22:46 ` Hans-Peter Nilsson [this message]
2015-07-23 18:24 MAINTAINERS: Update " Bernd Schmidt

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=alpine.BSF.2.00.1107071811090.21738@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@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).