I was imagining keeping the Message-ID, while having the first email also include the same value for In-Reply-To — I completely agree that removing the Message-ID would not work out. If the first email always included both fields, thus referencing itself as a reply to itself, I suppose there could be MUAs that would go into infinite loops. So, maybe too risky.

The only effect I can imagine of always setting the In-Reply-To would be to encourage threading where it's not currently happening, so removing the behavior and deleting all these little methods would be very attractive to me if it were my project. :)

It worked!

In T13265#245125, @brhodes wrote:

I merely wanted to have both possible resolutions on the table, one of which was to give the first message the ID later used In-Reply-To.

How old were things before the upgrade? (Roughly: less or more than about a year old?)

many megabytes or gigabytes … In some cases at Facebook, this command produced gigabytes of output.

My first response should be to step back and ask for a bit of context. Why is any truncation occurring here? My real preference would be to display the entire error output of the commands run, and if users dislike the verbosity, then they can dial back how much information is returned on an error or in the case of a crash. If a tool does decide that it needs, say, 4k of text to explain to the user what happened, then my preference would be that arc doesn't try to second-guess the tool, and simply prints all 4k of text.