Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200611155743.GC16376@fieldses.org> <CAADWXX9tV_khCjrO5eUJQry+QV4VLatt21KEkJ8irEcuqTbBsQ@mail.gmail.com>
 <20200611181141.GD16376@fieldses.org> <20200620165504.GG1514@fieldses.org>
In-Reply-To: <20200620165504.GG1514@fieldses.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat, 20 Jun 2020 11:10:22 -0700
Message-ID: <CAHk-=wg6KKyy-d0foGXguj1p1RtLg8mNNdeTHgs053rfAaAYPw@mail.gmail.com>
Subject: Re: [GIT PULL] nfsd changes for 5.8
To:     "J. Bruce Fields" <bfields@fieldses.org>
Cc:     "open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>,
        Chuck Lever <chuck.lever@oracle.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Sat, Jun 20, 2020 at 9:55 AM J. Bruce Fields <bfields@fieldses.org> wrote:
>
> Anyway, hopefully things are better now.

This email certainly looked fine. You had

    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; ...

with the proper headers ("From" shows up twice in your DKIM signature
list, and maybe you could add the message-id to the DKIM-protected
headers, but whatever), and google clearly liked the end result too:

       dkim=pass header.i=@fieldses.org header.s=default header.b=z+wyI4pO;

(and you already had the SPF records previously, and that continues to
pass too).

So from what I can tell, you're now doing everything you can to look
like a good modern non-spam email sender, and hopefully together with
having the Linode addresses cleared from Spamhaus there would be no
reason for gmail to ever hate you again.

In fact, you look better than most people. DKIM still isn't as common
as it perhaps should be.

Knock wood.

            Linus