git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Eric Wong <e@80x24.org>, git@vger.kernel.org
Subject: Re: vger not relaying some of Junio's messages today?
Date: Tue, 31 Jan 2017 12:27:44 -0800	[thread overview]
Message-ID: <xmqqpoj3q8jj.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170127040139.wz7xmizccjigz5ui@sigill.intra.peff.net> (Jeff King's message of "Thu, 26 Jan 2017 23:01:39 -0500")

Jeff King <peff@peff.net> writes:

> On Fri, Jan 27, 2017 at 03:57:53AM +0000, Eric Wong wrote:
>
>> I noticed both of these are are missing from my archives
>> (which rejects messages unless they come from vger):
>> 
>> <xmqq1svp7lcs.fsf@gitster.mtv.corp.google.com>
>> <xmqqefzp1d1x.fsf@gitster.mtv.corp.google.com>
>
> I don't have them either, so presumably vger ate them (I usually delete
> my cc copies after reading and keep the list ones, and I now have
> neither).
>
>> Not sure if there's something up with vger or Junio's setup because
>> other messages (even from Junio) are getting through fine.
>
> Sporadic failures, especially on a single topic, imply that something in
> the content may triggered the taboo filter (though often that takes out
> replies, too, which this doesn't seem to have done).

I think I figured this out yesterday.  

It was a dot somewhere in the name of a recipient on To:/Cc: line
that is NOT double-quoted.  For this thread, brian's human-readable
name "brian m. carlson" was double-quoted in the original I
responded to and it also was double-quoted in my response.
But there was another recipient with a dot after the middle initial,
which was NOT double-quoted in the original.  

My response seems to have been eaten because that name was not
double-quoted.  I saw that happen yesterday in another thread with
the same recipient, and resent with the only change to double-quote
that name and it went through.

  reply	other threads:[~2017-01-31 20:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27  3:57 vger not relaying some of Junio's messages today? Eric Wong
2017-01-27  4:01 ` Jeff King
2017-01-31 20:27   ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-06 17:46 Jonathan Tirado
2017-05-06 18:23 ` Samuel Lijin
2017-05-06 20:50   ` Eric Wong
2017-05-06 21:05     ` Ævar Arnfjörð Bjarmason
2017-05-06 21:42       ` Eric Wong
2017-05-08 10:42       ` Johannes Schindelin
2017-05-08 17:01         ` Brandon Williams
2017-05-09 10:10           ` Johannes Schindelin
2017-05-06 21:10     ` Samuel Lijin
2017-05-07  0:26       ` Eric Wong
2017-05-08 17:05         ` Brandon Williams
2017-05-07  1:05       ` Eric Wong
2017-05-07  3:00         ` Junio C Hamano
2017-05-07  3:24           ` Eric Wong
2017-05-07 12:41     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpoj3q8jj.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).