X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AC9BE3858C2B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1671499531; bh=dr4rjH+LQujdtub4QQ7SFi41xBZYaIdvihf56pSpz8M=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=JA0vw7b4V8yiMVwLsGLEmjRsbnlSHA4Xj5LyWP5mhptuyjArohg3e6TShqpRLc5n7 9CN66H3QkTrqxblLU3LWZTGvjmOG6I6K44f1/HE6YUWyxpenWlx/F/A68ZQZUQuWs3 UvuOVOUrzQsH/U5LS/sTdWMeVymLDoFzA7cep6Bc= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8CB6D3858D1E 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 Subject: Re: Mailing list subscription problems Content-Language: en-US To: cygwin AT cygwin DOT com References: <741ebccf-b2e5-507c-3d94-f26ac71dec45 AT gmail DOT com> In-Reply-To: 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 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Jim Garrison via Cygwin Reply-To: jhg AT acm DOT org Cc: Jim Garrison Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" 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 AT acm DOT org -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple