From: David Woodhouse <dwmw2@infradead.org>
To: jeremy@rootservices.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: SPF on kernel.org
Date: Sun, 06 Jun 2004 23:24:30 +0100 [thread overview]
Message-ID: <1086560670.29255.2.camel@localhost.localdomain> (raw)
In-Reply-To: <4864.68.254.2.84.1086559839.squirrel@webmail.rootservices.net>
On Sun, 2004-06-06 at 18:10 -0400, Jeremy D. May wrote:
> has SPF records even been thought of for kernel.org? maybe this is the
> wrong place to ask? if so, can i get the right place to ask about it.
SPF records would need to be on vger.kernel.org not on kernel.org. And
yes, this is the wrong place to ask. The right place would be
postmaster@vger.kernel.org. But I wouldn't bother -- it's manned by
people who have at least a modicum of clue, so I assume they won't do
anything as stupid as publishing SPF records. SPF is a fundamentally
broken mechanism which breaks valid email. It should not be encouraged
even by publishing no-op records ending in '?all'.
--
dwmw2
prev parent reply other threads:[~2004-06-06 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 22:10 SPF on kernel.org Jeremy D. May
2004-06-06 22:24 ` David Woodhouse [this message]
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=1086560670.29255.2.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=jeremy@rootservices.net \
--cc=linux-kernel@vger.kernel.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