From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from neet.inri.net ([107.191.102.52]) by ur; Mon Sep 26 10:40:30 EDT 2016 Received: (qmail 18284 invoked from network); 26 Sep 2016 14:39:49 -0000 Received: from mobile-166-170-222-004.mycingular.net (HELO ?127.0.0.1?) (sl@166.170.222.4) by neet.inri.net with SMTP; 26 Sep 2016 14:39:49 -0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: BlackBerry Email (10.3.2.858) Message-ID: <20160926144030.4399186.95743.13214@stanleylieber.com> Date: Mon, 26 Sep 2016 10:40:30 -0400 Subject: Re: [9front] (n)upas/ml quirks From: stanley lieber In-Reply-To: References: <20160926061747.4399186.40215.13125@stanleylieber.com> To: "cinap_lenrek@felloff.net" <9front@9front.org> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: framework-based package full-stack-oriented interface I'll try all these suggestions. I ran out of time yesterday. One note: The offending address was actually an *unsubscribe*: =C2=A0 =C2=A0 =C2=A0 =C2=A0 !host!username The original subscribe appeared in this format: =C2=A0 =C2=A0 =C2=A0 =C2=A0 user@host I was monitoring logs while sending test messages and it appeared=E2=80=8E that the message was accepted into the system but was never sent out to address-list. It also appeared that the list's pipeto was not fully processed; =E2=80=8Es= ome of the intermediate files created by the list's pipeto script never got created (until I removed the !host!user line from address-list). This makes me wonder if the failure occurred before sending was even attempted. As I say, I ran out of time, but the seeming failure to handle the address-list seemed like a clue. I think I recall previous observations of a similar failure: a mismatch between subscribes and unsunscribes results in failure, generally. I'll have more medium- to low-quality observations to report tonight. sl