LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

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

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

Print Reply
Ol' blue eyes <[log in to unmask]>
Thu, 21 Jul 1994 17:01:24 -0500
text/plain (57 lines)
        Nate Tassler posted this a week ago, but no one responded.
 
>BROWNVM just upgraded to Listserv 1.8a and I have noticed that
>sometimes users are now automatically deleted when mail bounces.
>What triggers this auto-deletion, and is there any way to turn
>it off?  In some cases I would prefer to let the problem get fixed,
>or set the user to nomail, without having to go through putting them
>back on the list and all.
 
        I too run a list based at brownvm, and have seen the same thing.  It
        seems to occur when the listserv can't find A records (see typical
        listing below), but does its thing *the first time it happens*.  Seems
        just a bit harsh...
 
        Note also that I've been seeing a lot of list messages originating from
        [log in to unmask] instead of directly from
        brownvm.brown.edu.  The sample below is one of them.  Does this relate
        to the auto-deletion?
 
-------------------------------------------------------------------------------
neal        [log in to unmask]                   412-624-0097 (office)
            [log in to unmask]                          412-624-7397 (fax)
                   Owner:   [log in to unmask]
              "Baseball (and Lesser Sports) Discussion List"
 
**********************  typical auto-delete message  *************************
 
The following users have been removed ("auto-deleted", in list owner jargon)
from the STATLG-L list as a  result of the nondelivery error report enclosed
below.  No action  is  required from  you;  this message  is  only for  your
information.
 
List of deleted users:
 
 address of deleted subscriber
 
This delivery error is in a special format that allows software like
LISTSERV to automatically take action on incorrect addresses; you can
safely ignore the numeric codes.
 
Note: delivery error converted to LMail format at BROWNVM.BROWN.EDU.
 
--> Error description:
Error-For:  address of deleted subscriber
Error-Code: 3
Error-Text: 550 Unable to find A records for any MX sites for the recipient
host
.
 
 
Error-End:  One error reported
 
----------------- Original delivery error (before conversion) -----------------
uga.cc.uga.edu unable to deliver following mail to recipient(s):
    <address of deleted subscriber>
550 Unable to find A records for any MX sites for the recipient host.

ATOM RSS1 RSS2