From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12036 invoked from network); 1 Oct 2023 04:24:37 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 1 Oct 2023 04:24:37 -0000 Received: from gaff.inri.net ([168.235.71.243]) by 9front; Sun Oct 1 00:20:18 -0400 2023 Received: from [127.0.0.1] ([168.235.81.125]) by gaff; Sun Oct 1 00:20:18 -0400 2023 Date: Sun, 01 Oct 2023 00:20:17 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <4F3D2C9093B9D1B31C1623A8A7A7B41A@eigenstate.org> References: <4F3D2C9093B9D1B31C1623A8A7A7B41A@eigenstate.org> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: overflow-preventing responsive event plugin API Subject: Re: [9front] upas/fs lstk(), one more time Reply-To: 9front@9front.org Precedence: bulk On October 1, 2023 12:13:41 AM EDT, ori@eigenstate=2Eorg wrote: >Quoth sl@stanleylieber=2Ecom: >> i backed up my mbox and added messages back in batches, checking after >> each batch that upas/fs was still able to open it=2E i did this until = i >> found a specific message upas/fs choked on=2E >>=20 >> sl > >is it possible to reproduce it with just that message? would >you be comfortable sending it over to someone for debugging? > > unfortunately, the precise message causing the problem turned out to conta= in sensitive information=2E i am pretty sure this is the first time upas/fs= has refused to index a message for me, but if it happens again, if possibl= e, i'll share the offending malformed message so we can name and shame the = villain=2E sl