Hi Chuck, Try these guys---www.addr.com. Everything you could want in a server: FP extensions, SSL, complete shell access, at least 70 megs of space, cgi/perl5, excellent tech support, *immediate usability*, on the "backbone", and currently $7.95 a month (when I joined 2 years ago it was $14.95 a month). I have sent many people there and have never had any tell me about any problems!! I installed the ringlink system, with customization in less that 10 minutes and it all works just fine even *sendmail*. Curt E. Angeledes Now a member of Because_Webring_Is_Broken Also accepting new rings at http://www.chief-moons-gallery.com/cmgrinklink.html Chuck Baslock wrote: > I hate to say this but at this point in time, I don't believe it "stopped" > working. > I believe it was disabled on purpose. > I no longer believe that netfirms can/or intends to provide the necessary > support we need(another Y!Webring?). > > I'm going to look for another ISP. > > Chuck > ----- Original Message ----- > From: "Daniel Gwozdz" <smage@together.net> > To: <ringlinklist@gunnar.cc> > Sent: Thursday, September 21, 2000 10:40 PM > Subject: RE: [ringlinklist] Re: NETFIRMS - EMAIL Fault for ringlink?? > > > > > I just sent a note to tech support as mine has stopped working too.. > > > > Daniel Gwozdz > > The Water-Cooled Volkswagen Ring - http://www.wcvw.org > > > > > >>>Above facility via send mail in cgi-bin does not appear > > > to have been operational from Netfirms for last 2 days > > > (since 18th September 2000) Anyone else had problems > > > please?? No problem re ringlink BEFORE this date. > > > I have two sites showing as being in queue, but received no > > > emails informing me of this. Have reported possible fault to Netfirms > > > >>> > > > > > > I was having problem with it for two days before that (the 16th). I've > > > asked their tech support about it, but no reply yet. Chuck Baslock also > > > has. No reply yet either, but other questions I've asked were handled > > > promptly. I can only guess they're trying to fix it. > > > I also tried using different email addresses. Apparently that didn't > > > work either.