Douglas Winship wrote:
>> Is there a way for a listowner to check on who is accessing the list
>> archives via the web? How about who is accessing via email?
Ben Parker wrote:
> Others have referred to useful information recorded in the LISTSERV log files.
> However these files are only available to the Site Adminstrator(s) and not to
> ordinary List Owner(s). So, at the limits of List Owner privileges, this
> information is not available.
Thank you. That is what I suspected. Why cannot a lisowner access this
information about his own list?
>> Is there a way to block web access from a particular site?
> Yes, this can be done at the List Owner level.
> The List Header Keyword is Service=
>
> For lists running the web archive interface: Starting with LISTSERV 1.8d it is
> possible to define "Service=" in terms of IP address blocks in order to limit
> access to list archive notebooks via the web archive interface. This is
> implemented as follows:
>
> 1. Notebook= ...,Service
> 2. "Service=" can contain entries of the form:
> [^]IP(a.b.c.d[/e])
>
> For example, if you know that the suspected 'bad actor' is has an IP address
> somewhere in the range 192.168.10.0/24 (a "Class C" in old terms) you could
> put
>
> Service= ^IP(192.168.10.0/24)
>
> in your list to deny WWW access to the list. But this would not prevent
> access by email queries.
Thank you, Ben, this is useful. I confess I never studied up too
particularly on the Notebook= keyword for other than the basics as the site
administrator generally does the setup on that and I tweak, very rarely,
minor things, usually at initial list setup and then let it run for years.
I will check on this. However, it would be helpful if the listowner could
check who is accessing his list's archives via the web, also via eamil.
Is there a way to block email access to the list archives, while allowing
a subscription and receipt of daily list postings? Say, cancel the
subscription's list password? (Speaking of which, why cannot listowners
establish a password for a subscriber having trouble doing so (say, they
can receive the list postings, but not job outputs, so can't confirm the
password)?).
Douglas Winship [log in to unmask]
|