1994-02-05 - how to solve this prob.

Header Data

From: garet.jax@nitelog.com (Garet Jax)
To: cypherpunks@toad.com
Message Hash: 48d5c18ebd84dfb9b243402f1d1694a34833faa0bd1b525088bd80068b37006d
Message ID: <cb.61524.10.0CD03BED@nitelog.com>
Reply To: <9401272306.AA26581@toad.com>
UTC Datetime: 1994-02-05 13:45:33 UTC
Raw Date: Sat, 5 Feb 94 05:45:33 PST

Raw message

From: garet.jax@nitelog.com (Garet Jax)
Date: Sat, 5 Feb 94 05:45:33 PST
To: cypherpunks@toad.com
Subject: how to solve this prob.
In-Reply-To: <9401272306.AA26581@toad.com>
Message-ID: <cb.61524.10.0CD03BED@nitelog.com>
MIME-Version: 1.0
Content-Type: text/plain



There MUST be some way that the LISTSERV software can be modified
so that a user can send an unsubscribe message to the -request line
for another user.

Take this Detweiler for example.  If he forgets where to send his
unsubscribe message and sends it to the list instead, someone could send
an unsubscribe message to the proper address for him. ex:

   'unsubscribe [ listname ] user@e-mail.addr'

The system would note that the name of the person sending the
unsubscribe message ( user1 ) was different from the one who was being
unsubscribed ( user2 ) , and would, after unsubscribing user2 send a
message to user2 telling him that he had been unsubscribed from the list
by user1. ex:

   'Dear user2, you have been unsubscribed from the Cypherpunks
   list by user1.  If you wish to resubscribe, send a message
   containing...'

That way, instead of the list readers bombarding the folks who send
the unsubscribe requests to the list, they could simply forward the
request to the proper place.

Now, how do we get it implemented?






Thread