Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Proportional Font
Show HTML Part by Default
Show All Mail Headers

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

Print Reply
Subject:
Re: Delivery error notice sent to LISTSERV
From:
Christian Reichetzeder <[log in to unmask]>
Reply To:
Forum on LISTSERV release 1.6
Date:
Wed, 25 Jul 90 12:13:38 SET
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
See
LISTSERV list.
 
On Mon, 23 Jul 90 09:35:11 EDT Postmaster said:
>Can anyone explain why this is failing?
   (see below for the question ....)
 
I can tell you what's failing - and  if it weren't also a little bit funny I'd
use other words.  The - err -  idiot who "produces" the  missing RFC821 (read:
BSMTP) envelope is  - guess who - MAILER@DEARN ...
Someone sent  a file to  be distributed  to the subscribers  of [log in to unmask]
Obviously the  RSCS tag  indicates RIOVM@DEARN as  originator. So  LISTSERV at
GITVM1 does  what every LISTSERV  would do: it  creates a DISTRIBUTE  job with
default headers  and this means  Ack=MAIL. Every  LISTSERV taking part  in the
distribution sends an acknowledgement to the  originator - RIOVM. RIOVM is not
able  to handle  mail (and  probably files)  to itself  in an  other way  than
sending  the mentioned  nastygram  which  is eventually  detected  as such  by
LISTSERV and sent to the postmaster(s).
The questions are:
* why does RIOVM send (non-mail) files?
* if RIOVM can't handle non-BSMTP files  the why does it send non-BSMTP files?
  The Received: line says that MAILER@DEARN processed a non-BSMTP file.
 
>
>----------------------------Original message----------------------------
>The  enclosed mail  file,  found  in the  LISTSERV  reader  ... mail  subject
>indicates a delivery problem.
>
>------------------------- Message in error (36 lines) -------------------------
>Received: from DEARN by OHSTVMA.IRCC.OHIO-STATE.EDU (Mailer R2.07) with BSMTP
> id 8956; Mon, 23 Jul 90 07:47:27 EDT
>Received: by DEARN (Mailer R2.07) id 9069; Mon, 23 Jul 90 13:27:54 CET
>Date:
>To:      <[log in to unmask]>
>From:    <[log in to unmask]>
>Subject: Undelivered mail
>
>    ***  Message from Gateway in Darmstadt ***
>RFC 821-Envelope is missing or incorrect
>
>-----------------------------------------------------------------------
>
>Received: from OHSTVMA.IRCC.OHIO-STATE.EDU by DEARN (Mailer R2.07) with BSMTP
> id 8258; Mon, 23 Jul 90 13:15:18 CET
>Received: by OHSTVMA (Mailer R2.07) id 8396; Mon, 23 Jul 90 06:58:06 EDT
>Date:         Mon, 23 Jul 90 06:58:03 EDT
>From:         Revised List Processor (1.6e) <[log in to unmask]>
>Subject:      Output of job "M3755." from LISTSERV@UKCC
>To:           [log in to unmask]
>
>File forwarded to LISTSERV@PUCC     for 377 recipients.
*------------- all following lines deleted -----------------*
 
Christian

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV