From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out0.migadu.com ([94.23.1.103]) by ewsd; Mon Sep 21 17:23:24 EDT 2020 Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a-b.xyz; s=key1; t=1600723395; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=7MOb+um/k7YX5w0CJxVfhuftihkbvb9m1oUPj2rx4+c=; b=iXsuKlymkyooZpG1iCq4eRp7bgkPGjadi4vld+IJu4FldCGNPqUsZsoA+gvHhNV+Xz+YCW m+0Ae61km5roJTJlz5suHvaTnar8YexUud5iucB9+HJyg12U7pRrQ4cw33Bes4SPASrkO0 NgmGeeC/yTeFuhS6Sv8yBFjiWg4BPp061GjY7t4Ew4q0RKqJhLzseluz1SP9gcTYbPtFZQ zU+8NdbKmnco0iYfVhWOFZmsE5xbJs9GQBCi3n3JwwsW2GQn9Mfmubh4aGo8KkLq263HZn mIXFrkwaQu8lKhw22Bl3dhdFTdEK6d3vW1lnSzYwQSOcGDPCzS8VC7ISVMaPwA== To: 9front@9front.org Subject: Re: *****SPAM***** [9front] test Date: Mon, 21 Sep 2020 23:23:12 +0200 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: kvik@a-b.xyz In-Reply-To: <20200921203300.GD43872@wopr> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Spam-Score: -0.10 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shared GPU GPU SOAP over JSON markup shader grid service Khm, I'm very confused with this email. I don't run SpamAssassin. Maybe my provider (Migadu) does but I don't know about it. More so, the problem here wasn't me getting mail from @9front.org but my mail sent to the list being sorted into Spam for (at least) the Gmail users. There were two things at play here: 1) @9front.org mailing list mangles the headers, like the subject line, without taking ownership of the mail. This causes my DKIM-signed mail to fail to verify at the receiver's end. 2) I had my DMARC policy set to 'reject', which tells the receiver to drop the faulty mail. Gmail chose to mark it as spam instead. Now that I have disabled this DMARC policy my mails through the list seem to arrive fine to everyone. I can't do anything about SUSPICIOUS NTLD, but I'll check what's up with the rDNS.