From nobody Tue Nov  8 14:56:05 2022
X-Original-To: freebsd-security@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N6B4S18fYz4XNgV;
	Tue,  8 Nov 2022 14:56:08 +0000 (UTC)
	(envelope-from rb@gid.co.uk)
Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250])
	by mx1.freebsd.org (Postfix) with ESMTP id 4N6B4R0jJgz3j1M;
	Tue,  8 Nov 2022 14:56:07 +0000 (UTC)
	(envelope-from rb@gid.co.uk)
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	spf=pass (mx1.freebsd.org: domain of rb@gid.co.uk designates 194.32.164.250 as permitted sender) smtp.mailfrom=rb@gid.co.uk;
	dmarc=none
Received: from smtpclient.apple (gw.br-thn-01.caladan.net.uk [80.71.4.65] (may be forged))
	by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 2A8Eu5Gn091971;
	Tue, 8 Nov 2022 14:56:05 GMT
	(envelope-from rb@gid.co.uk)
Content-Type: text/plain;
	charset=us-ascii
List-Id: Security issues <freebsd-security.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-security
List-Help: <mailto:freebsd-security+help@freebsd.org>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Subscribe: <mailto:freebsd-security+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-security+unsubscribe@freebsd.org>
Sender: owner-freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-22:13.zlib
From: Bob Bishop <rb@gid.co.uk>
In-Reply-To: <620a28b1-4c54-3eb5-2869-f8ecc86345aa@m5p.com>
Date: Tue, 8 Nov 2022 14:56:05 +0000
Cc: "freebsd-security@freebsd.org" <freebsd-security@FreeBSD.org>,
        FreeBSD Hackers <freebsd-hackers@FreeBSD.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <28957C58-7FD0-42DE-9395-13C02BB59240@gid.co.uk>
References: <20220830235803.BEF1110B7E@freefall.freebsd.org>
 <620a28b1-4c54-3eb5-2869-f8ecc86345aa@m5p.com>
To: George Mitchell <george+freebsd@m5p.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
X-Spamd-Bar: --
X-Spamd-Result: default: False [-2.70 / 15.00];
	NEURAL_HAM_LONG(-1.00)[-1.000];
	NEURAL_HAM_SHORT(-1.00)[-1.000];
	NEURAL_HAM_MEDIUM(-1.00)[-0.999];
	MV_CASE(0.50)[];
	R_SPF_ALLOW(-0.20)[+mx:c];
	MIME_GOOD(-0.10)[text/plain];
	RCVD_NO_TLS_LAST(0.10)[];
	MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org,freebsd-security@FreeBSD.org];
	R_DKIM_NA(0.00)[];
	MIME_TRACE(0.00)[0:+];
	ASN(0.00)[asn:42831, ipnet:194.32.164.0/24, country:GB];
	FROM_EQ_ENVFROM(0.00)[];
	ARC_NA(0.00)[];
	TO_DN_SOME(0.00)[];
	RCVD_COUNT_TWO(0.00)[2];
	FROM_HAS_DN(0.00)[];
	TO_DN_EQ_ADDR_SOME(0.00)[];
	TO_MATCH_ENVRCPT_SOME(0.00)[];
	RCPT_COUNT_THREE(0.00)[3];
	DMARC_NA(0.00)[gid.co.uk];
	TAGGED_RCPT(0.00)[freebsd];
	MID_RHS_MATCH_FROM(0.00)[]
X-Rspamd-Queue-Id: 4N6B4R0jJgz3j1M
X-ThisMailContainsUnwantedMimeParts: N

Hi,

> On 8 Nov 2022, at 14:42, George Mitchell <george+freebsd@m5p.com> =
wrote:
>=20
> On 8/30/22 19:58, FreeBSD Security Advisories wrote:
>=20
> > [four extremely delayed security notifications]
>=20
> It appears they all got hung up in mail queues on the machine named
> mlmmj.nyi.freebsd.org, arriving on that machine on August 9 in three
> cases and August 30 in the fourth.  Fortunately, notifications from
> the daily security run on my machine alerted me, though I was quite
> puzzled at the time to not see corresponding messages from the mailing
> list.  Their delayed arrival now makes me suspect that this was not
> an intentional policy decision.  Does anyone know what's up?
> -- George

Similarly several hundred messages from bugzilla-noreply@FreeBSD.org =
that hit my inbox this morning.

--
Bob Bishop
rb@gid.co.uk