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;
Date:   Sat, 20 Jun 2020 12:55:04 -0400
From:   "J. Bruce Fields" <bfields@fieldses.org>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     "open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>,
        Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [GIT PULL] nfsd changes for 5.8
Message-ID: <20200620165504.GG1514@fieldses.org>
References: <20200611155743.GC16376@fieldses.org>
 <CAADWXX9tV_khCjrO5eUJQry+QV4VLatt21KEkJ8irEcuqTbBsQ@mail.gmail.com>
 <20200611181141.GD16376@fieldses.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200611181141.GD16376@fieldses.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Thu, Jun 11, 2020 at 02:11:41PM -0400, J. Bruce Fields wrote:
> On Thu, Jun 11, 2020 at 10:42:19AM -0700, Linus Torvalds wrote:
> > I'm not entirely sure why, but gmail hates you and marked this as spam.
> > 
> > I (obviously) caught it despite that, but thought I'd mention it. I
> > assume it's lack of DKIM for fieldses.org.
> 
> Twenty years ago running my own mail service sounded like a fun idea.
> 
> Nowadays it's just this thing that means that, every now and then, I
> have to drop everything and go learn about some random bit of annoying
> tech, just so I can get on with my work or talk to my friends.  Then
> I'll promptly forget it, until years later it breaks, and I have to go
> relearn it all from scratch.
> 
> Anyway, googling DKIM....

By the way, I think the real problem might have been Spamhaus SBLCSS
listing my Linode server's IPv6 address.  I followed the suggestion at:

	https://www.spamhaus.org/faq/section/Spamhaus%20CSS#426

and requested a new /64 from Linode, added an IP from the new /64 to my
main interface, and updated AAAA and reverse DNS records.

I also set up DKIM (mainly following instructions from README.fedora in
the opendkim package).  Reading up a little more suggested DMARC is a
bad idea for my case.

Anyway, hopefully things are better now.

--b.