Skip to contentSkip to conversation

vger not relaying some of Junio's messages today?

DISCUSSION Eric Wong 3 participants 3 messages Jan 27, 2017 – Jan 31, 2017

lore
Share & tools
lore

Eric Wong

author
#0 lore raw

I noticed both of these are are missing from my archives (which rejects messages unless they come from vger):

<[email protected]>
<[email protected]>

https://public-inbox.org/git/[email protected]/#r

I only have them because I was Cc:-ed.

gmane doesn't seem to have them, either:

nntp://news.gmane.org/[email protected] nntp://news.gmane.org/[email protected]

Not sure if there's something up with vger or Junio's setup because other messages (even from Junio) are getting through fine.

#1 lore raw
Quoted 5 lines · Eric Wong

I noticed both of these are are missing from my archives (which rejects messages unless they come from vger):

<[email protected]>
<[email protected]>

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).

Quoted 2 lines

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).

-Peff

#2 lore raw
Quoted 12 lines · Jeff King
Quoted 5 lines · Eric Wong

I noticed both of these are are missing from my archives (which rejects messages unless they come from vger):

<[email protected]>
<[email protected]>

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).

Quoted 6 lines
Quoted 2 lines

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.