From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ewsd; Mon Sep 21 17:57:49 EDT 2020 Received: (qmail 49691 invoked by uid 1001); 21 Sep 2020 14:57:43 -0700 Date: Mon, 21 Sep 2020 14:57:43 -0700 From: Kurt H Maier To: 9front@9front.org Subject: Re: *****SPAM***** [9front] test Message-ID: <20200921215743.GF43872@wopr> Mail-Followup-To: 9front@9front.org References: <20200921213634.GE43872@wopr> <84CE96C81BD620937106B07893BCE92A@a-b.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84CE96C81BD620937106B07893BCE92A@a-b.xyz> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: agile SSL DOM STM rich-client framework On Mon, Sep 21, 2020 at 11:42:50PM +0200, kvik@a-b.xyz wrote: > I still don't understand whose SA you are talking about. >> Spam detection software, running on the system "vbsd.alarum.de" this one. It's far angrier about receiving mail (any mail) from a-b.xyz than any dkim-related problem. The DKIM errors contribute 0.2, the SPF failure contributes 0.9, the .xyz domain contributes 2.5, and the lack of accurate RDNS contributes 1.3. The default SA spam threshold is 5, so you're already at 3.8 just for any message at all from any xyz domain with bad RDNS. IMO the 'suspicious ntld' rule is egregious, and the only thing that you (kvik) should care about is fixing the server ident -- I think your system is identifying itself during SMTP handshake as 'a-b.xyz' when it should be identifying as 'ten.a-b.xyz' and nothing else should need to change. It's also possible that the mailserver at vbsd.alarum.de is failing to resolve ANY rdns, but I can't tell from the outside. If you want to get fancy you could add the 9front.org sending host to your SPF permissions and that would cure that, but I don't really think that's your problem. khm