At 11:01 PM 7/14/1997 -0700, you wrote:
>Thanks. The text follows, with real names omitted, save my own. This
>delivery error seems to have started, BTW, when we upgraded from Listserv
>1.8b to 1.8c. The error message appears to say two things: one, that a
>message was sent to the reserved mailbox; and two, that the message could
>not be delivered to a subscriber at SPRINTMAIL.COM. In fact, as I indicated
>earlier, the message was circulated to the list despite the delivery error.
>Moreover, the Sprintmail subscriber does receive messages from the list
AFAIK.

Here's the explanation.  Indeed the original message was distributed to the
subscribers by LISTSERV(R).

At least ONE of the messages bounced from a subscriber's mailbox.
Sprintmail sent the message back, ultimately to you.   If the problem at
sprintmail is intermittent, the user may only get a few of them bounced,
and would be unlikely to know that a few messages out of a bunch per day
didn't make it.


>-----------------------------------------------------
>
>The enclosed mail file has been identified as a delivery error for list
>DIST_ED because it was sent to the reserved 'owner-dist_ed' mailbox.

Various mail systems bounce messages in all sorts of weird ways due to bad
software, or more likely bad configuration.  You'd have to talk to
sprintmail about it, a job I'd never tackle.  Just ignore the bounce.   Not
your problem.


>
>------------------------------ Message in error -------
>Date: Mon, 14 Jul 97 22:12:44 PDT
>From: <[log in to unmask]>
>To: <[log in to unmask]>
>Subject: Undeliverable Mail
>
>ADMIN.ELCAMINO.CC.CA.US unable to deliver following mail to recipient(s):
>    <[log in to unmask]>
>ADMIN.ELCAMINO.CC.CA.US received negative reply:

Your machine didn't get a reply from sprintmail.  Details follow.

>553 Both To: and From: must be in form of: user@domain

Since you omitted the user name, can't prove it, but I'll bet there is
something wrong with the userid (the part left of the @sign), such as
having spaces in it, invalid characters, whatever.

Could also be a glitch with sprintmail.

Also, the received from a couple lines below looks fishy.  Note that the
machine that sent it back to you at elcamino does NOT have an FQDN.  That
is a sprintmail problem I'll bet.

Also, it is strange further below when "pentium" sent it to
admin.elcamino.......

Is "pentium" your machine running Eudora?  I'm amazed that it doesn't
require an FQDN or an ip number.  Maybe a config problem on your system?

Just food for thought.  And some of the others will chime in, I trust, in
case I'm off base on any of this.  I'm NOT the mail guru that Pete and Eric
and many others here are.

dan



>
>           ** Text of Mail follows **
>Received: from www-nt by ADMIN.ELCAMINO.CC.CA.US (IBM VM SMTP V2R3) with TCP;
>   Mon, 14 Jul 97 22:12:42 PDT
>Received: from LISTSERV.ELCAMINO.CC.CA.US by LISTSERV.ELCAMINO.CC.CA.US
>LISTSERV-TCP/IP release 1.8c) with spool id 0010 for
>[log in to unmask]; Mon, 14 Jul 1997 22:13:04 +0100
>Received: from pentium by ADMIN.ELCAMINO.CC.CA.US (IBM VM SMTP V2R3) with
TCP;
>          Mon, 14 Jul 97 22:12:39 PDT
>X-Sender: [log in to unmask]
>X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Message-ID:  <[log in to unmask]>
>Date:         Mon, 14 Jul 1997 22:17:36 -0700
>Reply-To:     DISTANCE EDUCATION DISCUSSION LIST
>              <[log in to unmask]>
>Sender:       DISTANCE EDUCATION DISCUSSION LIST
>              <[log in to unmask]>
>From:         Joseph Georges
>
Dan Lester
[log in to unmask]
In the kingdom of the blind, the one-eyed man is king.  Erasmus, 1534