From nobody Thu Apr 11 23:32:35 2024 X-Original-To: freebsd-stable@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 4VFwwS6wLYz5GMj5 for ; Thu, 11 Apr 2024 23:32:40 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.tutanota.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VFwwR3TwCz4F1Q for ; Thu, 11 Apr 2024 23:32:39 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tuta.io header.s=s1 header.b=n8UgOE+6; dmarc=pass (policy=quarantine) header.from=tuta.io; spf=pass (mx1.freebsd.org: domain of henrichhartzer@tuta.io designates 81.3.6.162 as permitted sender) smtp.mailfrom=henrichhartzer@tuta.io Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w1.tutanota.de (Postfix) with ESMTP id 023F1FBFC31 for ; Thu, 11 Apr 2024 23:32:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1712878355; s=s1; d=tuta.io; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=WAf+Hkkp/SdTMgPhYETY7W2ynvux/eBLoaFarJWy7z0=; b=n8UgOE+6ahwu2lh7PPMM9JpmmkGc1DvIEhvfIh5KB2E5K+WWULkl/E1XsZZ6M7do Sc3dd6EUnJGSsuNDuVpFFgq3En48qD5xFiQ2T3SWQAJCKvhwllnK76efYSehk88p6x8 b+XEC9HS6UUz1xRBzJwr8JP/l9Y9QrdIo9f/nK25aqTCq7NzDjVbxZxFspCCBdHo7EG ywHk6lISKPLZbBrD0C4Q2MQ/9bAxPPoygpdOdQ0P8UN3WokeXFEWXX7YspFZ22opy5L riaX1+6b2rIqY6yX/f1bl7Ld9ZCyONNTMrd99yWHrLnEiqRzs3YVEJTqoIdHhgN2ddU GyfnWJjaFg== Date: Fri, 12 Apr 2024 01:32:35 +0200 (CEST) From: henrichhartzer@tuta.io To: Freebsd Stable Message-ID: Subject: Can't find bootable partition List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.09 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[tuta.io,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:81.3.6.160/28]; R_DKIM_ALLOW(-0.20)[tuta.io:s=s1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[81.3.6.162:from]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; FROM_NO_DN(0.00)[]; ASN(0.00)[asn:24679, ipnet:81.3.0.0/18, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[tuta.io:+] X-Rspamd-Queue-Id: 4VFwwR3TwCz4F1Q Hi, I have 14.0-RELEASE installed with two drives in a ZFS mirror on a x86_64 system. I've been testing a very minor patch, rebooting, testing, etc. This is installed with EFI. Out of the blue, it won't come back. It detects both drives. I see these errors. zio_read error: 5 zio_read error: 5 zio_read error: 5 ZFS: i/o error - all block copies unavailable ZFS: failed to read pool zroot directory object Can't find /boot/zfsloader Can't find /boot/loader Can't find /boot/kernel/kernel I'm a little mystified. I know there were some talks of ZFS corruption. I was using the latest patches for the kernel, although world was from 14.0-RELEASE as it came out. I rebooted this probably a dozen times at least with no issue prior to this. Where should I start? Does this sound like I made some blunder or that the hardware randomly failed in some strange way? Thank you! -Henrich From nobody Fri Apr 12 00:09:58 2024 X-Original-To: freebsd-stable@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 4VFxlX3xWHz5GQXy for ; Fri, 12 Apr 2024 00:10:00 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162]) (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 (2048 bits)) (Client CN "mail.tutanota.de", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VFxlW3SqNz4HLQ for ; Fri, 12 Apr 2024 00:09:59 +0000 (UTC) (envelope-from henrichhartzer@tuta.io) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tuta.io header.s=s1 header.b=CIOLxWCd; dmarc=pass (policy=quarantine) header.from=tuta.io; spf=pass (mx1.freebsd.org: domain of henrichhartzer@tuta.io designates 81.3.6.162 as permitted sender) smtp.mailfrom=henrichhartzer@tuta.io Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w1.tutanota.de (Postfix) with ESMTP id 13E7FFBF814 for ; Fri, 12 Apr 2024 00:09:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1712880598; s=s1; d=tuta.io; h=From:From:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=RGW2qqPx+lwskj3yA4OgjKXSSUQCplWtbPh2SxVMp6Y=; b=CIOLxWCdAssXOA1bfzEkgiikTfvGzibKQn3OcMVvC41ezf/1JwiOOSuzwStfMR7Q 0yE0OaEhZpK5oX4EuRnExmEF02DiK3u8HSoCmP14NzrJDg8qWB4gLf2FM3kVvMt0W/j v6FmU+9goIuB07dG6RFN9WxySytVAT6dloswJhLEPB10e0yIh7a/+w3PoDAEb2j589f zd1G8YbGaD7heJABxaCu7Kf/mO6/hhJEYKgi/Dbz3fMf0TKCm8hmy1fmW384FLztc9k oXekjEzXeB0nxwPt4+8MgxwLhLLfR6ZZd/RfRFJivbIII1U1TJjaivBXkFje2IAMNM+ ZltsNbVR7g== Date: Fri, 12 Apr 2024 02:09:58 +0200 (CEST) From: henrichhartzer@tuta.io Cc: Freebsd Stable Message-ID: In-Reply-To: References: Subject: Re: Can't find bootable partition List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.10 / 15.00]; MISSING_TO(2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[tuta.io,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:81.3.6.160/28]; R_DKIM_ALLOW(-0.20)[tuta.io:s=s1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[81.3.6.162:from]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; FROM_NO_DN(0.00)[]; ASN(0.00)[asn:24679, ipnet:81.3.0.0/18, country:DE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[tuta.io:+] X-Rspamd-Queue-Id: 4VFxlW3SqNz4HLQ I booted the 14.0-RELEASE installer and mounted zroot to /tmp/mnt. There's nothing in the zroot, except other mounts (like /usr, /home, and /var, the defaults). Those appear to have good data. But there's no /tmp/mnt/COPYRIGHT, /tmp/mnt/boot, etc. I did a very lengthy memtest on this machine without issue. I don't have any particular reason to suspect hardware. It's as if every file/folder directly under zroot/ROOT/default has vanished. There's no zpool errors. I made no changes to the filesystem in the boot prior to the reboot. -Henrich Apr 11, 2024, 23:32 by : > Hi, > > I have 14.0-RELEASE installed with two drives in a ZFS mirror on a x86_64 system. I've been testing a very minor patch, rebooting, testing, etc. This is installed with EFI. > > Out of the blue, it won't come back. > > It detects both drives. I see these errors. > > zio_read error: 5 > zio_read error: 5 > zio_read error: 5 > ZFS: i/o error - all block copies unavailable > ZFS: failed to read pool zroot directory object > > Can't find /boot/zfsloader > Can't find /boot/loader > Can't find /boot/kernel/kernel > > I'm a little mystified. I know there were some talks of ZFS corruption. I was using the latest patches for the kernel, although world was from 14.0-RELEASE as it came out. > > I rebooted this probably a dozen times at least with no issue prior to this. > > Where should I start? Does this sound like I made some blunder or that the hardware randomly failed in some strange way? > > Thank you! > > -Henrich > From nobody Sun Apr 14 22:33:05 2024 X-Original-To: freebsd-stable@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 4VHlSg40xfz5HCG4 for ; Sun, 14 Apr 2024 22:33:23 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from exhmta01.bpe.bigpond.com (exhmta01.bpe.bigpond.com [203.42.40.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VHlSd3jYCz562D for ; Sun, 14 Apr 2024 22:33:20 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bigpond.net.au header.s=202303 header.b="wRw+EIM "; dmarc=pass (policy=reject) header.from=bigpond.net.au; spf=pass (mx1.freebsd.org: domain of areilly@bigpond.net.au designates 203.42.40.145 as permitted sender) smtp.mailfrom=areilly@bigpond.net.au DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bigpond.net.au; s=202303; h=To:Date:Message-Id:Subject:Mime-Version: Content-Type:From; bh=MRFDLhiV6Rs2CebojrCCpVrz8BlwXZDCW9QzTNkyWbk=; b=wRw+EIM Doaz5HMxO+BoroisesIVsTEt5is1dYkg04TQ0vKq8iFQovE2Vp9Pg7IDoU+xMx74Ulnl/uWROWf0G mIjvpEbUOn9i6gUwt9bXwMxxMn9zEFkkMtBZ83zCDCDXlOGPp2bNGGIBosE2Kv3uQ2WqBcc4jFviw z+0VUAUYn2k7/RxkLn6Oly2VYRFal/9ddcZWlNf/xtgufVD6aCqZRmLNoWwj7isifdMBPt+UREzPD hoPMsi0J7eYslEyAS1oK/+2KzPSHSUDiU6SpgbKnh4X/mNgrdtgILr5CQA6blJaZkgS0EDQ15av5n 6Kt61ELrfHsoQP7ncpgUNl/eW9Q==; Received: from exhprdcmr07 by exhprdomr01 with esmtp (envelope-from ) id 1rw8PV-00082U-2s for freebsd-stable@freebsd.org; Mon, 15 Apr 2024 08:33:16 +1000 Received: from [121.223.155.16] (helo=smtpclient.apple) by exhprdcmr07 with esmtpa (envelope-from ) id 1rw8PU-0009kZ-1K for freebsd-stable@freebsd.org; Mon, 15 Apr 2024 08:33:16 +1000 From: Andrew Reilly Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: What's happening to Sender: headers? Message-Id: Date: Mon, 15 Apr 2024 08:33:05 +1000 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3774.500.171.1.1) X-tce-id: areilly@bigpond.net.au X-tce-ares-id: e{4661114d-e266-400f-baa8-f4095bd124f4}1 X-tce-spam-action: no action X-tce-spam-score: 0.0 X-Cm-Analysis: v=2.4 cv=R4kFG8RX c=1 sm=1 tr=0 ts=661c59ac a=g7JjhvAvvPZ9ycLFhywHJA==:117 a=g7JjhvAvvPZ9ycLFhywHJA==:17 a=IkcTkHD0fZMA:10 a=raytVjVEu-sA:10 a=6I5d2MoRAAAA:8 a=sOHWvEidyx_mBR3m3sIA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 X-Cm-Envelope: MS4xfHV/3nbWLpWB9Ofq2PUejyrxmE85X86ihvMHGpJmuqfNt2ijlk54gt5VgL1Vz6RPuqeArBZjZV+6TudAwvNBrb3THc4Yb/wyQSlC42xpOokk3QRK26D/ q+z//jm/KXtJBi+OO+nwUd6WIRTbSmYZbe6+Ej+pagHYmT/G1PaRcwEDpMoruLTUEOrP3b02PkDNPg== X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.25 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.75)[-0.746]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[bigpond.net.au,reject]; R_DKIM_ALLOW(-0.20)[bigpond.net.au:s=202303]; R_SPF_ALLOW(-0.20)[+ip4:203.42.40.128/25]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:1221, ipnet:203.40.0.0/13, country:AU]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[bigpond.net.au]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; FREEMAIL_ENVFROM(0.00)[bigpond.net.au]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[bigpond.net.au:+] X-Rspamd-Queue-Id: 4VHlSd3jYCz562D Hi all, I can=E2=80=99t think of anywhere else to ask, but this knowledgeable = group is as likely as any to know what=E2=80=99s going on, I think. For years and years I=E2=80=99ve been able to filter all of my FreeBSD = mailing list messages into a separate FreeBSD inbox with a pair of = simple dovecot-sieve rules: if address :matches "Sender" "*owner@freebsd.org" { fileinto = "in.freebsd"; } elsif address :matches "Sender" "owner*@freebsd.org" { fileinto = "in.freebsd"; } (=E2=80=A6 and similarly for most of my other mailing lists). The = Sender header is (used to be) a reliable reflection of the envelope FROM = address, which reliably tied things to the email server sending the list = messages. On about the 11th or 12th of April, a significant chunk of FreeBSD = mailing list messages, including especially the git commit messages, = started showing up in my normal INBOX, evading the filter rules. Over the weekend I got around to investigating, and discovered that the = errant messages don=E2=80=99t _have_ a Sender: header. There=E2=80=99s = a Return-Path: header that captures the envelope-from, but I haven=E2=80=99= t figured out how to make sieve check that yet: it doesn=E2=80=99t seem = to like it. Sieve documentation is spectacularly inconclusive, but I = suspect that the envelope extension might do what I want, but that=E2=80=99= s not really my question. Does anyone know why the Sender: header, which used to be so reliable = that I had thought it an intrinsic part of the SMTP/MTA ecosystem, has = gone away, or is at least not ubiquitous? I=E2=80=99m running dovecot and pigeonhole and postfix from ports, on = stable/14 and feeding messages in using fetchmail rather than direct = SMTP: I=E2=80=99ve found that exposing an SMTP endpoint requires more = anti-spam fu than I've been prepared to muster so far. Using fetchmail = is clunky but it keeps me behind my ISP=E2=80=99s spam filter. Cheers, Andrew From nobody Sun Apr 14 23:49:32 2024 X-Original-To: freebsd-stable@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 4VHn8q4w16z5HK1H for ; Sun, 14 Apr 2024 23:49:47 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VHn8q02fQz443Z for ; Sun, 14 Apr 2024 23:49:46 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (123-1-21-232.area1b.commufa.jp [123.1.21.232]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 43ENnWQu078836; Mon, 15 Apr 2024 08:49:32 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 15 Apr 2024 08:49:32 +0900 From: Tomoaki AOKI To: Andrew Reilly Cc: freebsd-stable@freebsd.org Subject: Re: What's happening to Sender: headers? Message-Id: <20240415084932.b912e002e79bdc38b68189d7@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4VHn8q02fQz443Z On Mon, 15 Apr 2024 08:33:05 +1000 Andrew Reilly wrote: > Hi all, > > I can’t think of anywhere else to ask, but this knowledgeable group is as likely as any to know what’s going on, I think. > > For years and years I’ve been able to filter all of my FreeBSD mailing list messages into a separate FreeBSD inbox with a pair of simple dovecot-sieve rules: > > if address :matches "Sender" "*owner@freebsd.org" { fileinto "in.freebsd"; } > elsif address :matches "Sender" "owner*@freebsd.org" { fileinto "in.freebsd"; } > > (… and similarly for most of my other mailing lists). The Sender header is (used to be) a reliable reflection of the envelope FROM address, which reliably tied things to the email server sending the list messages. > > On about the 11th or 12th of April, a significant chunk of FreeBSD mailing list messages, including especially the git commit messages, started showing up in my normal INBOX, evading the filter rules. > > Over the weekend I got around to investigating, and discovered that the errant messages don’t _have_ a Sender: header. There’s a Return-Path: header that captures the envelope-from, but I haven’t figured out how to make sieve check that yet: it doesn’t seem to like it. Sieve documentation is spectacularly inconclusive, but I suspect that the envelope extension might do what I want, but that’s not really my question. > > Does anyone know why the Sender: header, which used to be so reliable that I had thought it an intrinsic part of the SMTP/MTA ecosystem, has gone away, or is at least not ubiquitous? > > I’m running dovecot and pigeonhole and postfix from ports, on stable/14 and feeding messages in using fetchmail rather than direct SMTP: I’ve found that exposing an SMTP endpoint requires more anti-spam fu than I've been prepared to muster so far. Using fetchmail is clunky but it keeps me behind my ISP’s spam filter. > > Cheers, > > Andrew You'd better contacting postmaster@freebsd.org. Or, this is not the case though, file a bug on bugzilla.freebsd.org with Product = "Services" and Component = "Mailing Lists". This is helpful is your emails are somehow rejected by freebsd.org mail server. -- Tomoaki AOKI