On 14 Nov 99, 8:53, Dennice wrote:

> >> SUBSCRIBE ALLERGY Dennice NoneofyourBusiness

Real subtle, Dennice. <droll>

I was once kicked off a Listserv by the owner by using a silly 
non-name.  If you want to be anonymous, just make up a fake name.

Listserv also allows you to send in a command that hides your address 
from other subscribers.  This, however, is becoming less necessary 
because most owners today suppress the subscriber list from all but 
themselves.

> > Sorry,  the ALLERGY  list  has  been locked  since  99/11/12 21:14  by
> > [EMAIL PROTECTED] Try again later and contact the list owner if the
> > condition persists.

...and the answer is:

---paste copy---

Date:         Thu, 11 Nov 1999 01:50:58 -0800
Reply-To:     Allergy Discussion Group <[EMAIL PROTECTED]>
Sender:       Allergy Discussion Group <[EMAIL PROTECTED]>
From:         Ballew Kinnaman <[EMAIL PROTECTED]>
Subject:      Allergy ADMIN: Allergy Will Temporarily Close Tomorrow
Comments: cc: [EMAIL PROTECTED]
Content-Type: text/plain; charset="us-ascii"

 Dear Allergy Folks,
 With a most heavy heart, I must inform you that tomorrow the Allergy 
Discussion Group on LISTSERV at TAMU.EDU will close - after five years 
of continuous, wonderful, informative, educational, and supportive 
daily allergy-realted interactions between as many as 925 members in as 
many as 42 countries.

 A&M Has Been Great

 Texas A&M University has been a generous and supportive home for 
Allergy for all of these five years, and I am full of warmth and 
appreciation for all that TAMU.EDU has done for me and for Allergy 
through these many months and years. Please know that I will never 
forget these wonderful years at TAMU - and there will always be a soft, 
warm part of my heart that remembers with deep gratitude Allergy's 
founding host site.

 Why Is Allergy Closing?

 To make a long story short, a single former member of the Rubber 
LISTSERV (my other discussion group at TAMU.EDU) wrote an irrelevant 
complaint (about a Web page on a completely private server 50 miles 
away from the A&M campus) to the Texas A&M administration. This 
apparently brought both Allergy and Rubber to their attention. Because 
A&M now has a firm rule that requires a local A&M campus "sponsor" 
(student, staff, or faculty) for each LISTSERV, and because Allergy has 
none, Allergy is no longer eligible to be served by the A&M LISTSERV 
host.

 I regret that one disgruntled former member of Rubber can have so much 
negative influence on all the members of Allergy, and I very much 
regret any inconvenience that this lapse in service will provide for 
any of ya'll. I hope that Allergy can return to service very soon. I 
particularly regret that Allergy received only 48 hours notice to find 
a sponsor or close, because some of you may find it difficult on such 
short notice to find alternative sources of allergy-related fellowship, 
current information and support.

 Search For New Host - Commercial Support

 Allergy will remain closed until another host, or perhaps a Texas A&M 
sponsor, is found. I expect this closure to be anywhere from a few 
weeks to perhaps until the beginning of next year (2000).

 Several options are under consideration, and NO decision is yet made 
about whether to use Listbot, Onelist/Egroups, Lyris, LISTSERV or 
something else. If commercial support is readily found, Allergy will 
begin again, in a new "incarnation," very soon. If Allergy is to remain 
a volunteer operation without significant commercial support, as it has 
for most of its five years, it will take longer to re-configure and 
move the operation to another server, etc.

[...rest snipped...]

---end copy---

Okay, allergy sufferers, let's go to PLAN B.  We leave the University 
of A&M and go to the University of Arkansas, now.

I believe this is the same Allergy list now on a UARK.EDU server:

TO: [EMAIL PROTECTED]
SUBJECT: {Leave Blank}
BODY: SUBSCRIBE ALLERGY yourfirstname yourlastname

Let me know if that gives you a problem, too.  If so, we'll have to go 
to PLAN C, I guess. :-)

Alan
[EMAIL PROTECTED]

Reply via email to