From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Fri Oct  2 23:55:09 -0400 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id ac0df9d3 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Fri, 2 Oct 2020 20:54:59 -0700 (PDT)
Message-ID: <9048AE54735DB36DC9F19F44BDE6C36A@eigenstate.org>
To: sirjofri+ml-9front@sirjofri.de, 9front@9front.org
Subject: =?utf-8?q?Re:_[9front]_=E2=80=9Cempty=E2=80=9D_mail_(possible_unimportant_bug)?=
Date: Fri, 02 Oct 2020 20:54:58 -0700
From: ori@eigenstate.org
In-Reply-To: <53db3d4d-6996-4bf7-8dc2-0e6208693489@sirjofri.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: social social enhancement engine method-scale deep-learning lifecycle software 

> Hey ori,
> 
> The quoted mail is from /mail/box/username/mbox/stuff.
> 
> The log line (/sys/log/smtpd) is this:
> 
> oat Oct  2 11:16:06 ++[gmail.com/104.148.61.185] blocked: mail refused: 
> illegal header chars: fd out of range or not open
> 
> Seems like the mail is indeed refused and thus empty, but it still 
> creates an empty mail in /mail/box.

Ok -- that's a bug, but it makes sense. That error comes from
smtpd.c:/^pipemsg(), which means we've already started feeding
it into the delivery pipeline. don't think we're losing messages,
just creating spurious empty ones.

I'm not sure when I'll get to it, but I think it'll be easy enough
to do -- maybe kill the process we're piping to on a garbled message,
or don't open the pipe until we've parsed the headers.