From nobody Fri Aug 4 20:21:31 2023 X-Original-To: freebsd-net@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 4RHcYn0M3jz4h2VX for ; Fri, 4 Aug 2023 20:21:33 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4RHcYm2qslz4VBx; Fri, 4 Aug 2023 20:21:32 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 374KLVBR094239; Fri, 4 Aug 2023 21:21:31 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 374KLV4u094238; Fri, 4 Aug 2023 21:21:31 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202308042021.374KLV4u094238@donotpassgo.dyslexicfish.net> Date: Fri, 04 Aug 2023 21:21:31 +0100 Organization: Dyslexic Fish To: jamie@catflap.org, bapt@freebsd.org Cc: guru@unixarea.de, freebsd-net@freebsd.org Subject: Re: Bouncing messages from freebsd-net@FreeBSD.org References: <1691031051-56818-mlmmj-5f44a9f8@FreeBSD.org> <202308031500.373F0mYX024048@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Fri, 04 Aug 2023 21:21:32 +0100 (BST) X-Spamd-Result: default: False [-0.33 / 15.00]; NEURAL_SPAM_SHORT(0.66)[0.659]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; NEURAL_HAM_MEDIUM(-0.29)[-0.286]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; FREEFALL_USER(0.00)[jamie]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4RHcYm2qslz4VBx Baptiste Daroussin wrote: > No it was not sent to the whole list but only to the people whom mail server > have bounced an incoming mail. Apologies. I should have checked the header more closely. I've never had one of these before, and I received one the same time as I saw the posting from Matthias about the same thing. > It is not a configuration, this can happen in 2 cases: > - a change in the on your email provider which start bouncing emails (hence the > fact we don't stop those emails) > - but most case it is due to the antispam on your provider side, when a spam > managed to passthrough our (freebsd) antispam infrastructure. I run my own mailservers - The only antispam measure I use is the spamhaus SBL. I just checked the log - my end refused it because of: 2023 Aug 2 17:26:25 donotpassgo sm-mta[60105]: 372GQP6W060096: SYSERR(root): Too many hops 27 (25 max): from via mx2.freebsd.org, to (The same for 3720 and 3719) > To receive the email that has bounced: > > mail freebsd-net+get-3719@freebsd.org (not that there is a good chance that it > bounces again if this was not a configuration change that has been fixed. Tried that, and it bounced again, same message. > and raw version: > https://lists.freebsd.org/archives/freebsd-net/2023-August/003718.txt If you look at that, it appears that the message was sent out from the list to a subscriber, where it looped a few times, and then got injected back into the freelist - this is presumably why a few people got the bounce. Cheers, Jamie