In the last couple of minutes I've gotten messages like this from
10 different mailing list managers.  I think this is the latest
lamer scheme to make busy people more miserable to no gain.

Eric: if someone arranges for two LISTSERVs to serve each other
out like this, will they continue to exchange jobs as they should?
Or will it break the backbone?

De
------------------------------------------------------------------------------
Return-Path: [log in to unmask]
Received: from msu.edu (ibm.cl.msu.edu [35.8.2.2])
         by manethos.miep.org (8.8.4/8.8.4) with SMTP
         id RAA29375 for <[log in to unmask]>; Fri, 21 Feb 1997 17:02:43 -05
00 (EST)
Message-Id: <[log in to unmask]>
Received: from MSU.EDU by msu.edu (IBM VM SMTP V2R3) with BSMTP id 7191;
         Fri, 21 Feb 97 17:02:52 EST
Received: from MSU.EDU (NJE origin LISTSERV@MSU) by MSU.EDU (LMail V1.2a/1.8a)
with BSMTP id 7288 for <[log in to unmask]>; Fri, 21 Feb 1997 17:02:52 -0500
Date:    Fri, 21 Feb 1997 17:02:52 EST
To:      Dennis Boone <[log in to unmask]>
From:    "L-Soft list server at Michigan State University (1.8b)"
<[log in to unmask]>
Subject: Problem processing mail file from [log in to unmask]

An error occurred while processing file 5971 from [log in to unmask]: "Mail
has been  received on the  LISTSERV mailbox from a  user which had  been served
out".

------------------- Message causing the problem (89 lines) --------------------
Return-Path: <[log in to unmask]>
Received: from MSU (NJE origin SMTP2@MSU) by MSU.EDU (LMail V1.2a/1.8a) with
          BSMTP id 7286; Fri, 21 Feb 1997 17:02:52 -0500
Received: from fensende.com by msu.edu (IBM VM SMTP V2R3) with TCP;
   Fri, 21 Feb 97 17:02:47 EST
Received: (from daemon@localhost)
          by fensende.com (8.8.4/8.8.4)
          id OAA26573; Fri, 21 Feb 1997 14:03:43 -0800 (PST)
Date: Fri, 21 Feb 1997 14:03:43 -0800 (PST)
Message-Id: <[log in to unmask]>
To: [log in to unmask]
From: [log in to unmask]
Subject: Majordomo results: Output of your job "Majordomo"
Reply-To: [log in to unmask]

--

>>>> > --
**** Command '>' not recognized.
>>>> Unknown command - "--". Try HELP.
**** Command 'unknown' not recognized.
>>>>
>>>> You had  20 tries.  From now on  your requests will  be ignored  without
 any
**** Command 'you' not recognized.
>>>> reply. You can restore your access to LISTSERV by having another person
 send
**** Command 'reply.' not recognized.
>>>> the following command to [log in to unmask]: SERVE [log in to unmask]
**** Command 'the' not recognized.
>>>>
>>>> All subsequent commands have been flushed.
**** Command 'all' not recognized.
>>>>
>>>> Summary of resource utilization
**** Command 'summary' not recognized.
>>>> -------------------------------
END OF COMMANDS
**** Help for [log in to unmask]:

This is Brent Chapman's "Majordomo" mailing list manager, version 1.93.

In the description below items contained in []'s are optional. When
providing the item, do not include the []'s around it.

It understands the following commands:

    subscribe [<list>] [<address>]
        Subscribe yourself (or <address> if specified) to the named <list>.

    unsubscribe [<list>] [<address>]
        Unsubscribe yourself (or <address> if specified) from the named <list>.

    get [<list>] <filename>
        Get a file related to <list>.

    index [<list>]
        Return an index of files you can "get" for <list>.

    which [<address>]
        Find out which lists you (or <address> if specified) are on.

    who [<list>]
        Find out who is on the named <list>.

    info [<list>]
        Retrieve the general introductory information for the named <list>.

    lists
        Show the lists served by this Majordomo server.

    help
        Retrieve this message.

    end
        Stop processing commands (useful if your mailer adds a signature).

Commands should be sent in the body of an email message to
"[log in to unmask]"or to "<list>[log in to unmask]".

The <list> parameter is only optional if the message is sent to an address
of the form "<list>[log in to unmask]".


Commands in the "Subject:" line NOT processed.

If you have any questions or problems, please contact
"[log in to unmask]".