vger vs GitGitGadget, was Re: [PATCH v3 1/1] t0001: fix on case-insensitive filesystems

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 25, 2019, 10:50 UTC
Message-ID: <nycvar.QRO.7.76.6.1906251147581.44@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqqftnyhkyu.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 24 Jun 2019, Junio C Hamano wrote:

Show 11 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > ---
> >
> > 	Again, re-sending, as something in the mail (my guess is the
> > 	non-ASCII character in Martin's surname) seems to upset vger so
> > 	much that it drops the mail unceremoniously.
>
> Hmph, but in the copy I am responding to, I can see non-ASCII
> Martin's surname in the CC: header just fine, so vger may not
> be at fault, perhaps?

You can see the non-ASCII surname fine because you are responding to my reply, which I sent via Alpine.

The original mail was sent by GitGitGadget via nodemailer, using GMail's SMTP end point, and the fact that _I_ received it means that it was partially successful in delivering that mail.

I can only assume that GMX or Alpine did something to the mail that made it look better to vger.

*goes-to-unleash-the-power-of-investigation*

So I have a theory now why vger regurgitated on that mail: it had the unquoted name brian m. carlson in the Cc: line.

Expecting that this is the culprit, I opened https://github.com/gitgitgadget/gitgitgadget/pull/98 to fix that.

Thanks, Dscho