[CLUE-Tech] Mail Delivery (failure clue-tech@clue.denver.co.us)

[Roy J. Tellason]

On Thursday 08 July 2004 11:26 am, Charles Oriez wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At 10:38 AM 7/8/2004 -0400, Roy J. Tellason wrote:
> >On Thursday 08 July 2004 07:38 am, match at dimensional.com wrote:
> >
> >(Apparently the attachment,  "message.scr" didn't make it to the reply...)
> >
> >WTF?  Bad enough I get this crap showing up in my inbox,  but to have it
> > come in on a mailing list?  I didn't know you guys allowed binary
> > attachments.
> >
> >This needs to be fixed.  Or unsubscribe me,  one or the other.

> It never reached me.
>
> You didn't reproduce the headers.  Are you sure that it came through the
> list?
>
> This header:
> Received: from clue.denver.co.us (clue.denver.co.us [216.38.207.181])
> is needed on anything that came through the list.  A forgery most likely
> won't have that

Here's a direct cut-and-paste:

Received: from psmtp.com (exprod5mx54.postini.com [12.158.34.233])
        by procyon.blazenet.net (8.12.8/Mine) with SMTP id i68Bdaoj025858
        for <rtellason at blazenet.net>; Thu, 8 Jul 2004 07:39:37 -0400 (EDT)
Received: from source ([216.38.207.181]) by exprod5mx54.postini.com 
([12.158.34.245]) with SMTP;
        Thu, 08 Jul 2004 04:39:36 PDT
Received: from clue.denver.co.us (IDENT:mailman at localhost.localdomain 
[127.0.0.1])
        by clue.denver.co.us (8.9.3/8.9.3) with ESMTP id FAA14163;
        Thu, 8 Jul 2004 05:29:11 -0600
Received: from clue.denver.co.us (proxy-sabata-ejp.powernet.cz 
[193.109.183.94])
        by clue.denver.co.us (8.9.3/8.9.3) with ESMTP id FAA14151
        for <clue-tech at clue.denver.co.us>; Thu, 8 Jul 2004 05:28:50 -0600
From: match at dimensional.com

You'll notice that the header you mention is in there.  Maybe it didn't reach 
you because something upstream of you stopped it.  Me,  I have my upstream 
stuff set to NO filtering,  having had some bad experiences with providers 
screwing with my communications in the past being way too heavy-handed about 
such stuff (and switching providers a few months back because they told me 
that they _couldn't_ turn it off completely).