Sure.....here are all the header lines... John Return-Path: <[log in to unmask]> Received: from woodchuck.uvm.edu (woodchuck.uvm.edu [132.198.101.174]) by penguin1.uvm.edu (8.12.10/8.12.10) with ESMTP id i9TItXak027420; Fri, 29 Oct 2004 14:55:33 -0400 Received: from eagle.uvm.edu (eagle.uvm.edu [132.198.101.203]) by woodchuck.uvm.edu (8.12.11/8.12.11) with ESMTP id i9TItTQi018056; Fri, 29 Oct 2004 14:55:29 -0400 (envelope-from [log in to unmask]) Received: from list.uvm.edu (raccoon.uvm.edu [132.198.101.191]) by eagle.uvm.edu (8.12.11/8.12.11) with ESMTP id i9TIicZt015728; Fri, 29 Oct 2004 14:55:29 -0400 Received: from LIST.UVM.EDU by LIST.UVM.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 450812 for [log in to unmask]; Fri, 29 Oct 2004 14:55:28 -0400 Precedence: bulk Received: from groundhog.uvm.edu (groundhog.uvm.edu [132.198.101.185]) by list.uvm.edu (8.12.8/8.12.8) with ESMTP id i9TItSJc005681 for <[log in to unmask]>; Fri, 29 Oct 2004 14:55:28 -0400 Received: from jmnet21 ([211.244.156.249]) by groundhog.uvm.edu (8.12.11/8.12.11) with SMTP id i9TItQqe008387 for <[log in to unmask]>; Fri, 29 Oct 2004 14:55:27 -0400 (envelope-from [log in to unmask]) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_D65_FD642471.D219711B" X-Priority: 2 X-Mailer: IXQ Mailer Version 3.32 Message-ID: <059a01c4bde8$f0a37321$59b63a93@jmnet21> Date: Sat, 30 Oct 2004 03:49:12 +0900 Reply-To: CIT staff discussion list <[log in to unmask]> Sender: CIT staff discussion list <[log in to unmask]> From: "Ashlyn J. Nadeau" <[log in to unmask]> Subject: She will love you for this. To: [log in to unmask] Parts/Attachments: On Mon, 1 Nov 2004 [log in to unmask] wrote: > On Mon, 01 Nov 2004 10:53:38 EST, John Ryder said: > > Here's a partial mail header, with valid From and To lines: > > > > Date: Sat, 30 Oct 2004 03:49:12 +0900 > > From: Ashlyn J. Nadeau <[log in to unmask]> > > To: [log in to unmask] > > Subject: She will love you for this. > > Parts/Attachments: > > Umm.. Could we please see *ALL* the header lines (in particular, the Received: > headers)? It's quite possible that this message never went anywhere *near* > the Listserv - it was dumped directly into your mailbox with forged from/to.... >