dwmw2 at infradead.org
Sun Jan 29 11:30:34 EST 2012
On Sun, 2012-01-29 at 15:36 +0000, John Rose wrote:
> Date: Mon, 23 Jan 2012 17:00:55 +0000
> Message-ID: <CACns58WO=-HjgU0cYtGdptKr7+bMfH7iYA=vBfRyYg68fnBOng at mail.gmail.com>
> Subject: Re: Naive questions: RTMP packets & output
> From: John Rose <john.aaron.rose at gmail.com>
I looked up this one. It arrived at my systems, and you received a
response almost immediately thereafter:
2012-01-23 17:00:58 +0000 1RpNGM-0008Kx-4R <= john.aaron.rose at gmail.com H=mail-wi0-f177.google.com [22.214.171.124] P=esmtps X=TLSv1:RC4-SHA:128 S=3277 id=CACns58WO=-HjgU0cYtGdptKr7+bMfH7iYA=vBfRyYg68fnBOng at mail.gmail.com
2012-01-23 17:00:58 +0000 1RpNGM-0008Kx-4R => get_iplayer <get_iplayer at lists.infradead.org> R=mailman_here_router T=mailman_transport
2012-01-23 17:00:58 +0000 1RpNGM-0008Kx-4R Completed
2012-01-23 17:01:01 +0000 1RpNGP-0008Lh-6T <= get_iplayer-bounces at lists.infradead.org H=localhost (merlin.infradead.org) [::1] P=esmtp S=1331 id=mailman.1723.1327338059.14259.get_iplayer at lists.infradead.org
2012-01-23 17:01:02 +0000 1RpNGP-0008Lh-6T => john.aaron.rose at gmail.com R=lookuphost T=verp_smtp H=gmail-smtp-in.l.google.com [126.96.36.199] X=TLSv1:RC4-SHA:128 C="250 2.0.0 OK 1327338062 i8si6126435vdv.59"
2012-01-23 17:01:02 +0000 1RpNGP-0008Lh-6T Completed
It does look like it was trapped for moderation, for whatever reason.
Mailman's logs say (they're local time and the machine is in Toronto),
so 5 hours difference):
Jan 23 12:00:59 2012 (14259) get_iplayer post from john.aaron.rose at gmail.com held, message-id=<CACns58WO=-HjgU0cYtGdptKr7+bMfH7iYA=vBfRyYg68fnBOng at mail.gmail.com>: Message has a suspicious header
The confusing thing is that it's gone from the moderation queue now. I
don't know how that would have happened unless you'd clicked the
'discard' link you get in the response email.
I did actually find the message in the spam filter's cache, where it
keeps messages for training. A close inspection seems to indicate that
it was a reply, but it lacked In-Reply-To: and References: threading
headers. How did you actually post that? Whatever you did, something
broke the normal reply process...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5818 bytes
Desc: not available
More information about the get_iplayer