From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.jhmg.net (smtp.jhmg.net [147.182.185.113]) by sourceware.org (Postfix) with ESMTPS id 8CB6D3858D1E for ; Tue, 20 Dec 2022 01:24:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8CB6D3858D1E Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=jhmg.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jhmg.net Received: from [192.168.10.7] (c-71-236-214-188.hsd1.or.comcast.net [71.236.214.188]) (Authenticated sender: jhg) by smtp.jhmg.net (Postfix) with ESMTPSA id E65CF60B25 for ; Tue, 20 Dec 2022 01:24:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jhmg.net; s=smtp; t=1671499493; bh=k4nqGu1hgQTvWRQznXoJqRvnGI2bajkcpXh1DEOXZmk=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To:From; b=I6k4fAuH64YndiQqU4oviz2UyWiwTYUndwcJ9nARTr/i4JB3HuWCX/JHUiy7I+Set pYKpSFYHoZ0uEFVkdKMZVRQ1ay4a9DTX/gdAlUmXqtM4rYMg4bzYokVa6FYYSAGt9H +K4vgeOGz3rlRlQZTdMZvuJsnVxqTkRTqnmcAFkw= Message-ID: <9c22b0d4-bf92-269b-82e9-a9e7e9121dc1@jhmg.net> Date: Mon, 19 Dec 2022 17:24:52 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.6.0 Reply-To: jhg@acm.org Subject: Re: Mailing list subscription problems Content-Language: en-US To: cygwin@cygwin.com References: <741ebccf-b2e5-507c-3d94-f26ac71dec45@gmail.com> From: Jim Garrison In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 12/19/22 11:42, Corinna Vinschen via Cygwin wrote: >> > Actually, Google hasn't relaxed their filtering, rather the DNS record > of the cygwin.com domain was the culprit. It didn't have the required > (by Google) DKIM/SFP records. This has been rectified last week, > fortunately, so this shouldn't happen again. I re-enabled mail for > all accounts having been disabled due to bounces. Off-topic but I can't resist :-) The real irony here is that while Google has draconian anti-SPAM filtering for _incoming_ mail, they are now one of the leading senders of SPAM, and emails to their abuse address bounce. Sigh! (I'll shut up now) -- Jim Garrison jhg@acm.org