This is sent primarily to the LSTSRV-L list, but also to the MAIL-L list
in order to get comments concerning mail header formats with respect to
a major problem.
 
An infinite growing loop will occur with LISTSERV sending mail to UMASS
on BITNET if the user has no file space for the mail.  Their mailing system
returns the rejection to the userid identified in the SENDER field.
What should be done to prevent this loop from occuring and allow the
users at UMASS to receive mailings via UMASS?
 
The following is a copy of the response from their systems programmer;
below that is the actual message received the first time in the loop:
 
------------ ENCLOSED MESSAGE 1 ------------
Message-ID: <861124114136.00001703.ABET.MA@UMass> (UMass-Mailer 4.03)
Date:     Mon, 24 Nov 86  11:41:36 EST
From:     Shores@UMass  (Ken Shores)
Subject:  UMass mail server
To:       Phil@uiucvmd
 
    The student who is receiving the "Info-Hams" list from you passed
along your comments about the "malfunction" in the UMass mail system to
me.  Our mail system is performing according to RFC822, when an error
occurs it returns an error message to the name in the "Sender" field.
 
    I refer you to section 4.4.4 of RFC822 "Automatic use of
From/Sender/Reply-to" which states:
 
    .The "Sender" field mailbox should be sent notices of any problems
     in transport or delivery of the original messages.
 
and also to section 4.4.2 "Sender/Resent-Sender", which states, in part:
 
    "...it is strongly recommended that when a computer program generates
a message, the HUMAN who is responsible for that program be referenced as
part of the "Sender" field mailbox specification."
 
    In sum, the problem is that your mailer, or some processor that you
use, is placing the name "I-HAMS-L@UIUCVMD" in the sender field.  What it
should have placed here is "I-HAMS-REQUEST@wherever" so that the error
replies would be directed to the manager of the list, and not to a list
processor.  If you fix the contents of your "Sender" field there will be
no problem with bounced messages.
 
        Ken Shores
        Systems Programmer
        University Computer Center
        University of Massachusetts
 
P.S.  The reason the message bounced in the first place was that the student
      who was recieving the list had insufficient space for all of the copies
      he wanted to keep.  When/If he increases his file space he will no longer
      bounce copies of the list.
 
BITNet:   Shores@UMass
ARPA:     [log in to unmask]
Phone:    (413) 545-2690
 
------------ ENCLOSED MESSAGE 2 ------------
Date:         22 Nov 86 22:19:59 EST
Reply-To:     <[log in to unmask]>
Sender:       "Distribution of [log in to unmask]" <I-HAMS-L@UIUCVMD>
Comment:      Due to the length of the permanent file, you cannot send to notes
Comment:      file "
From:         NETWORK MAIL SERVER <SERVER@UMASS>
Subject:      Undeliverable message
 
+--------------------------------+
: A copy of your message follows :
+--------------------------------+
 
Received: by UMass via BITNet with NJF for RADIO@UMass; 22 Nov 86 22:14:54 EDT
Received: by UIUCVMD (Mailer X1.23) id 9196; Sat, 22 Nov 86 20:53:11 CST
Date:     22 Nov 86 17:33:28 GMT
Reply-To: [log in to unmask]
Sender:   I-HAMS-L@UIUCVMD
X-To:         <[log in to unmask]>
From:     [log in to unmask]
Subject:  yaesu ft290 mark 2 question
To:       [log in to unmask]
 
Has anyone out in net land got the chance to try out the new yaesu ft290r mark 2
 2 meter radio? If so I would be interested in your comments on the equipment,
 pro/con etc. Thhanks much. 73...Dave n2aam