Mailing List Archive

Mailing List: cavers

Banner Advert

Message Display

From: "Rich Lesperance" <richl@uf*.ed*>
To: "Cave listserv" <cavers@cavers.com>
Subject: Fw: Error: ListServer Message to Mailing List
Date: Sat, 21 Aug 1999 01:45:12 -0400

----- Original Message -----
From: <owner-cavers@aquanaut.com>
To: <richl@uf*.ed*>
Sent: Friday, August 20, 1999 8:28 PM
Subject: Error: ListServer Message to Mailing List


> Your message (included below) was sent to the `cavers' distribution
> address, but it looks very much like you meant it for the list server.
> Following Internet conventions, the server can be reached by sending
> to the `cavers-request' address.  Use the `cavers' address only for
> messages indended for distribuition to all readers of the list.
>
> If your message WAS meant for distribution, the presence of the words
> `approve', `help', `subscribe', `unsubscribe', `index', `send', `who',
> `test', or `quit' at the start of your message have confused the program.
> Please indent the lines in question, or try making the message longer.
>
> Please resend your message to the appropriate address.
>
> --
> Send mail for the `cavers' mailing list to `cavers@aquanaut.com'.
> Send subscribe/archive requests to `cavers-request@aquanaut.com'.
>
> > From owner-cavers@opal.com Fri Aug 20 20:27:57 1999
> > Received: from fulton.opal.com (root@lo*)
> > by fulton.opal.com (8.9.3/jr3.6) with EXEC for cavers
> > id UAA29714; Fri, 20 Aug 1999 20:27:57 -0400
> > Received: from zen.kr.com (kr.com [204.96.46.12])
> > by fulton.opal.com (8.9.3/jr3.6) with ESMTP for <cavers@aquanaut.com>
> > id UAA29707; Fri, 20 Aug 1999 20:27:53 -0400
> > Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108])
> > by zen.kr.com (8.9.0/8.9.0) with ESMTP id UAA15596
> > for <cavers@cavers.com>; Fri, 20 Aug 1999 20:20:52 -0400 (EDT)
> > Received: from host (ppp-04-ts20.nerdc.ufl.edu [128.227.73.72])
> > by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with SMTP id UAA19644
> > for <cavers@cavers.com>; Fri, 20 Aug 1999 20:22:25 -0400
> > Message-ID: <000801beeb6a$a01760e0$4849e380@ho*>
> > From: "Rich Lesperance" <richl@uf*.ed*>
> > To: "Cave listserv" <cavers@cavers.com>
> > Subject: Re: aquanaut.com
> > Date: Fri, 20 Aug 1999 20:17:57 -0400
> > MIME-Version: 1.0
> > Content-Type: multipart/alternative;
> > boundary="----=_NextPart_000_0005_01BEEB49.17F191C0"
> > X-Priority: 3
> > X-MSMail-Priority: Normal
> > X-Mailer: Microsoft Outlook Express 5.00.2014.211
> > X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
> >
> > This is a multi-part message in MIME format.
> >
> > ------=_NextPart_000_0005_01BEEB49.17F191C0
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > I've noticed some problems recently with both techdiver and the =
> > cavelist. I emailed them, and got this rapid reply from JR Oldroyd, so =
> > hopefully the problem will be shortly fixed:
> >
> > Rich L
> >
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> >
> > Thanks for all the info.
> >
> > We did more analysis here and we have figured out the problem.  It is
> > totally unrelated to the mail processor.  It is due to a new client
> > having started processes on their machine that are sucking network
> > bandwidth like you wouldn't believe.  That is draining resources from
> > our mail processor and all the other services.
> >
> > It'll be a week or so while we give this client a chance to fix things
> > and/or we get additional bandwidth to the mail processor.  =
> > Unfortunately,
> > things won't improve much before then.  So, please bear with us.
> >
> > This is the first time this has happened.  We have had other problems
> > (such as the mail processor shutting down completely) but this is a
> > new problem.  The good thing is that we can solve it, albeit not for
> > a week or so.
> >
> > Thanks for letting me know about this.  Actually, you're the only one
> > who's mentioned it so far.
> >
> >
> >
> > ------=_NextPart_000_0005_01BEEB49.17F191C0
> > Content-Type: text/html;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > <HTML><HEAD>
> > <META content=3D"text/html; charset=3Diso-8859-1" =
> > http-equiv=3DContent-Type>
> > <META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
> > <STYLE></STYLE>
> > </HEAD>
> > <BODY bgColor=3D#ffffff>
> > <DIV><FONT size=3D2>I've noticed some problems recently with both =
> > techdiver and=20
> > the cavelist. I emailed them, and got this rapid reply from JR Oldroyd,
=
> > so=20
> > hopefully the problem will be shortly fixed:</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2>Rich L</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT=20
> >
size=3D2>>>>>>>>>>>>>>>>>=
> >
>>>>>>>>>>>>>>>>>>&=
> > gt;></FONT></DIV>
> > <DIV><FONT size=3D2></FONT> </DIV>
> > <DIV><FONT size=3D2>Thanks for all the info.</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2>We did more analysis here and we have figured out
=
> > the=20
> > problem.  It is<BR>totally unrelated to the mail processor.  =
> > It is due=20
> > to a new client<BR>having started processes on their machine that are =
> > sucking=20
> > network<BR>bandwidth like you wouldn't believe.  That is draining =
> > resources=20
> > from<BR>our mail processor and all the other services.</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2>It'll be a week or so while we give this client a
=
> > chance to=20
> > fix things<BR>and/or we get additional bandwidth to the mail =
> > processor. =20
> > Unfortunately,<BR>things won't improve much before then.  So, =
> > please bear=20
> > with us.</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2>This is the first time this has happened. 
We =
> > have had=20
> > other problems<BR>(such as the mail processor shutting down completely)
=
> > but this=20
> > is a<BR>new problem.  The good thing is that we can solve it, =
> > albeit not=20
> > for<BR>a week or so.</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2>Thanks for letting me know about this.  =
> > Actually, you're=20
> > the only one<BR>who's mentioned it so far.</FONT></DIV>
> > <DIV> </DIV>
> > <DIV><FONT size=3D2></FONT> </DIV></BODY></HTML>
> >
> > ------=_NextPart_000_0005_01BEEB49.17F191C0--
> >

Navigate by Author: [Previous] [Next] [Author Search Index]
Navigate by Subject: [Previous] [Next] [Subject Search Index]

[Send Reply] [Send Message with New Topic]

[Search Selection] [Mailing List Home] [Home]