LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Dustin Fu <[log in to unmask]>
Thu, 18 Nov 1993 14:49:58 CST
text/plain (71 lines)
I have received about 140+ delivery error report from
VMTECSLP.SLP.ITESM.MX's MAILER (The original message is attached at the
end.)  I could not figure out why this happened.  I appreciate if you all
can help me to figure out why.  Thanks in advance.
 
Dustin Fu
Academic Computing Services
U of Tx at Arlington
 
~~~~~~~~~~~~~~~~~~~~~~~~~original message~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Return-Path: <@UTARLVM1.UTA.EDU:[log in to unmask]>
Received: from UTARLVM1.UTA.EDU (NJE origin LISTSERV@UTARLVM1) by
          UTARLVM1.UTA.EDU (LMail V1.1d/1.7f) with BSMTP id 8660; Wed,
          17 Nov 1993 14:43:22 -0600
Date:         Wed, 17 Nov 1993 14:43:22 -0600
From:         BITNET list server at UTARLVM1 (1.7f) <[log in to unmask]>
Subject:      Delivery error report from VMTECSLP.SLP.ITESM.MX
To:           Dustin Fu <[log in to unmask]>
X-LSV-ListID: None
 
The enclosed  mail file, found in  the LISTSERV reader and  shown under the
spoolid 3519 in the console log, has been identified as a possible delivery
error notice for the following reason: mail  origin seems to be a mailer or
mail-daemon.
 
------------------------- Message in error (43 lines) -------------------------
Return-Path: <>
Received: from VMTECSLP.SLP.ITESM.MX (NJE origin MAILER@VMTECSLP) by
          UTARLVM1.UTA.EDU (LMail V1.1d/1.7f) with BSMTP id 8658; Wed,
          17 Nov 1993 14:43:19 -0600
Received: from VMTECSLP.SLP.ITESM.MX (NJE origin MAILER@VMTECSLP) by
 VMTECSLP.SLP.ITESM.MX (LMail V1.1d/1.7f) with BSMTP id 0027; Wed,
 17 Nov 1993 14:43:52 -0400
Date:     Wed, 17 Nov 1993 14:41:09 -0400
Reply-To: [log in to unmask]
From:     RFC822 mailer (LMail release 1.1d/1.7f) <[log in to unmask]>
Subject:  Undelivered mail - RFC822 parser log
To:       [log in to unmask]
 
Your message was rejected by the RFC822 parser. The following errors were
reported by the parser:
 
<W> Invalid RFC822 field - "//RMUSIC-L JOB
    Echo=No,Reply-to="[log in to unmask]"". Rest of header flushed.
<E> "From:"/"Sender:" field is missing.
 
------------------------- Rejected message (22 lines) -------------------------
//RMUSIC-L JOB Echo=No,Reply-to="[log in to unmask]"
//To DD *
A15919 ITESO BSMTP
GY195002 ITESMVF1 BSMTP
/*
// DIST2 MAIL I=Y FROM=RMUSIC-L@GITVM1 FORW(CRC) HOST(273 288) PATH(273: 288:)
//Via DD "GITVM1 UGA RICEVM1 UTARLVM1"
//CRC DD "2-86CE43BE"
//Data DD *,EOF
Date:         Wed, 17 Nov 1993 09:48:42 -0800
Reply-To:     Music Discussion List <[log in to unmask]>
Sender:       Music Discussion List <[log in to unmask]>
From:         Uncle Scott <[log in to unmask]>
Subject:      That "O" thing.
To:           Multiple recipients of list RMUSIC-L <[log in to unmask]>
 
I've seen in postings for a while the use of an "O" at the end of a word or
too.  It's suttle, almost subliminalO.  When I read it out loud, it
sounds kinda funnyO.
 
Just Curious,
Uncle Scotty.

ATOM RSS1 RSS2