Re: [9front] (n)upas/ml quirks

[stanley lieber <sl@stanleylieber.com>]

I'll try all these suggestions. I ran out of time yesterday.

One note:

The offending address was actually an *unsubscribe*:

        !host!username

The original subscribe appeared in this format:

        user@host

I was monitoring logs while sending test messages and it appeared‎
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; ‎some
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