From owner-freebsd-test@freebsd.org Sun Jan 24 06:40:17 2021 Return-Path: Delivered-To: freebsd-test@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2F59F4F0880 for ; Sun, 24 Jan 2021 06:40:17 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNjzj0nYzz4bfM; Sun, 24 Jan 2021 06:40:17 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [IPv6:2a00:1098:82:3a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id EBCDC2087C; Sun, 24 Jan 2021 06:40:16 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [95.216.22.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 4DNjzh1cdlz1wtV; Sun, 24 Jan 2021 06:40:16 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 4DNjzf5dghz6FW8; Sun, 24 Jan 2021 06:40:14 +0000 (UTC) From: "Philip Paeps" To: "Mark Millard" Cc: freebsd-test@freebsd.org Subject: Re: Failure Notice (attempt to send to freebsd-test@lists.freebsd.org was rejected so trying freebsd-test@freebsd.org) Date: Sun, 24 Jan 2021 14:40:10 +0800 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.14r5757) Message-ID: <13EC55D0-19F5-4F36-8F49-AAA41EAE3F8E@freebsd.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-test@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Test posting area List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2021 06:40:17 -0000 On 2021-01-24 14:36:33 (+0800), Mark Millard wrote: > On 2021-Jan-23, at 22:29, Philip Paeps wrote: > >> On 2021-01-23 22:25:03 (-0800), Mark Millard via freebsd-test wrote: >>> Begin forwarded message: >>> >>>> From: "Philip Paeps" >>>> Subject: Re: Failure Notice (attempt to send to >>>> freebsd-test@lists.freebsd.org was rejected) >>>> Date: January 23, 2021 at 22:13:51 PST >>>> To: "Mark Millard" >>>> >>>> Thanks for trying ... and I've clearly not had enough coffee. >>>> >>>> The correct address is freebsd-test@freebsd.org. :-) >>>> >>>> Could you try that again please? Sorry about that! >>>> >>>> Philip >>> >>> No problem: I'll try the other email address. >> >> Thank you! >> >> Interesting ... freebsd-test is configured identically to >> freebsd-current but *does* the DMARC munging correctly. >> I really have no idea what's going on with the freebsd-current list. > > Any chance that it is associated with listing more than > one list (cross posting)? That was what I thought originally. When we first noticed the problem, it was a message you cross-posted to freebsd-arm@ and freebsd-current@. The freebsd-arm@ list was misconfigured to not munge. I've since fixed that. Your most recent message to freebsd-current@ was sent only to that list though, and it wasn't munged. And freebsd-current@ definitely has munging configured. Looking more closely, I can't actually find evidence of any address munging on freebsd-current@ ... so that list is behaving badly. Mystifying. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises