On Fri, 19 Dec 1997 14:43:27 -0600, Brian Crawford <[log in to unmask]> wrote:

>>------------------------ Message in error (80 lines)
>>--------------------------
>>Received: from listserv.oit.unc.edu by home.ease.lsoft.com (LSMTP for
>>Windows NT v1.1a) with SMTP id <[log in to unmask]>; Wed, 17
>>Dec 1997 11:18:33 -0500
>>Received: from daemon@localhost (fake: [log in to unmask] (port
>>2716) ([152.2.25.135])) by listserv.oit.unc.edu with ESMTP id
>><222176-17387>; Wed, 17 Dec 1997 11:17:04 -0500
>>Received: by email.unc.edu id <1038-148720>; Wed, 17 Dec 1997 11:17:32 -0500
>>Date:  Wed, 17 Dec 1997 11:17:31 -0500 (EST)
>>Sender:  <[log in to unmask]>
>>Fake-Sender: Edward P Gardner <[log in to unmask]>
>>From:  Edward P Gardner <[log in to unmask]>
>>X-Sender: [log in to unmask]
>>To:    "St. Louis Cardinals Baseball Mailing List"
>><[log in to unmask]>


Since this has just cropped up suddenly, I would say it is a problem most likely
with the campus mail system.  Somebody thought it would be a "Good Thing" to so
identify mail coming out of the campus mail spool as coming from 'daemon@...'
when this is NOT smart (even if true in this case) and LISTSERV is not the only
program that will apply filters to stop mail in this case.  Primarily it's an
effort to prevent runaway mail loops.

Forward the entire msg hdrs and your explanation of the problem to
[log in to unmask] and let them sort it out there.  There is
nothing for LISTSERV itself or LSMTP to do here.
--
 __________________________________________________________________
 Ben Parker ..... L-Soft international Inc. ..... [log in to unmask]