LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
Brian Crawford <[log in to unmask]>
Fri, 19 Dec 1997 14:43:27 -0600
text/plain (67 lines)
I have a real person at unc.edu who has been unable to post to my list
because of the [log in to unmask] address which appears in his email headers.
His user id is not daemon, but it appears in the header as sender: like
this:

>------------------------ 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]>
>Subject: Re: [CARDINALS] Mercker signing bad sign for Benes?
>In-Reply-To: <[log in to unmask]>
>Message-ID: <[log in to unmask]>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII


This just started in the past week.

Brian Crawford
Chicago

-----------------

At 11:29 AM -0600 12/19/97, Ben Parker wrote:
>On Fri, 19 Dec 1997 10:52:01 EST, Elliott Parker <[log in to unmask]>
>wrote:
>
>>A server has started using "[log in to unmask]" in the sender line.
>>    Will Listserv accept this?  A subscriber has been trying to
>>change their list configuration, but she is not getting any response
>>from Listserv and her commands are not acted on.  She does get
>>messages from the list.
>>    I seem to remember some discussion that addresses like root and
>>daemon are ignored, but I can't find anything in the documentation.
>
>
>It is not documented, but 'daemon' is assumed to be a (runaway) machine
>process
>and not a human.  Like 'postmaster' and certain other words it is part of the
>standard LISTSERV "filter" and will not be passed or acted upon.  For obvious
>reasons we will not document all the possible words in this filter.
>
>This same query has already shown up elsewhere.  If it is a real person (about
>which we begin to have some doubt) they simply must change their userID to be
>acceptable to LISTSERV.
>
>--
> __________________________________________________________________
> Ben Parker ..... L-Soft international Inc. ..... [log in to unmask]


--------------------------------------------------------------
Brian Crawford                                            Chicago
[log in to unmask]

ATOM RSS1 RSS2