From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 9147 invoked from network); 31 May 2021 15:39:45 -0000 Received: from hurricane.the-brannons.com (2602:ff06:725:1:20::25) by inbox.vuxu.org with ESMTPUTF8; 31 May 2021 15:39:45 -0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTP id a25be1c8 for ; Mon, 31 May 2021 08:39:40 -0700 (PDT) Received: from localhost ( [2602:3f:e0f9:dc00::2]) by hurricane.the-brannons.com (OpenSMTPD) with ESMTPSA id 3e74c76f (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Mon, 31 May 2021 08:39:12 -0700 (PDT) From: Chris Brannon To: edbrowse-dev@edbrowse.org Subject: edbrowse-dev mailing list changes Date: Mon, 31 May 2021 08:39:11 -0700 Message-ID: <87im2yhq00.fsf@the-brannons.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List MIME-Version: 1.0 Content-Type: text/plain Some of you are going to get this message multiple times. I've tried to limit the blast radius, but I apologize in advance if you see more than one of these. Last night, I noticed I'm having deliverability issues to Google. As part of the fix, I'm changing my mailing list infrastructure so that it won't insert [listname] prefixes in subject lines. This is to help DKIM-signed messages to validate properly. I'm also going to start rolling out DKIM signing of messages originating from my own domains, in the hope that it will help them get through to people using gmail. I wouldn't be surprised if I made additional changes, but hopefully all of that will be in the background. If you rely on a [listname] prefix in subject lines to filter mail, you should be able to filter on the List-Id: header instead.