[ale] OT: BellSouth FastAccess DSL

[John Wells]

I have a friend who can't get out on port 25 to anywhere from a Earthlink
DSL.  I would also point you to this:
http://www.dslreports.com/shownews/492
Of course, this is outgoing mail, so I may indeed have had my facts
wrong...going what I've been told by others.  I personally have never used
Earthlink.  Still, it causes him quite a bit of problems, as he can't
relay through his company's server.

As it happens, I do a large amount of web application development across
my BellSouth DSL to servers in Las Vegas.  No problems with caching here
at all.

John



James P. Kinney III said:
> You heard wrong.
>
> I do have a static IP address, but I run a web server and mail server
> from an Earthlink DSL line.
>
> I have a client who has a dynamic IP Earthlink DSL (basic home package)
> and they can access their squirellmail with no problems (dyndns) from
> anywhere in the world (until the DSL "modem" died from lightning.
> Earthlink is sending a replacement at no charge).
>
> Bellsouth uses aggressive html caching which causes immense problems for
> remote web application development.
>
> On Fri, 2002-11-08 at 19:24, John Wells wrote:
>> >From what I hear, Earthlink blocks some ports, specifically port 80
>> and
>> port 25 (sendmail).  That, in my opinion, sucks.
>>
>> John
>>
>> Robert Heaven said:
>> > This is the reason I went with Earthlink/Mindspring because they
>> seem to be able to get BellSouth to get off their back-sides and get
>> things done. And, I don't have to worry about the PC Police raiding
>> my house looking for a non-Windows box on the network.
>> >
>> > On Fri, 2002-11-08 at 14:17, Jeff Hubbs wrote:
>> >> Well, I had a similar problem with Telocity/DirecTV - carrier just
>> vanished one day and it never returned - and I felt that Bellsouth
>> was the reason why.  BS simply never responded to DirecTV's
>> requests and they absolutely, totally would not talk to me.  Of
>> course, they'd be happy to if I became a Bellsouth customer, but
>> after that, I simply wasn't inclined to give them any more of my
>> money.  I didn't feel it was right for them to disconnect a DSL
>> circuit and then only give it back if I switched to BS.  I'm really
>> loath to ever be dependent on them again for Internet service.
>> >>
>> >> - Jeff
>> >>
>> >> On Fri, 2002-11-08 at 13:21, Fulton Green wrote:
>> >> > Naturally, this is an off-list reply since I didn't want to start
>> >> yet another flamefest on ALE ...
>> >> >
>> >> > I'm not all that happy about choosing B$, but I'm doing it
>> because
>> >> back in March, back when I had DirecTV DSL (ne'e Telocity), which I
>> had previously been happy with, I had noticed some severe technical
>> difficulties with the service that wound up making the service
>> barely usable only during late night (and unusable all other
>> times). I complained to DirecTV, who routed the request to B$, who
>> found an issue in their line and corrected it. A week later, I had
>> the same problem, so I complained again, and B$ came out to my
>> complex and told DirecTV that it was my inside wiring. DirecTV then
>> offered to add a special "data line" between the complex box and my
>> apt., but that if that wound up fixing the problem, I'd be out
>> $150. Being barely able to scrape up food and gas money on an
>> unemployment benefits budget, I punted.
>> >> >
>> >> > So now, I figure that if I have those same probs, BellSouth will
>> be
>> >> more active in trying to fix them while I have their service. I'll
>> see just what exactly I lose if I don't do the full 12-mo.
>> >> commitment, then choose a more amenable (i.e.,
>> >> non-PPPoE-authenticating) provider, or maybe by then my credit
>> rating will be good enough such that I don't have to pay an extra
>> deposit for AT&T Comcast.
>> >> >
>> >> > On Fri, Nov 08, 2002 at 01:04:43PM -0500, Geoffrey wrote:
>> >> > > I personally wouldn't ever choose Bellsouth for any service.
>> >> There  customer service is non-existent, they're arrogant and,
>> plain just don't  care.
>> >> >
>> >> > ---
>> >> > This message has been sent through the ALE general discussion
>> list.
>> >> See http://www.ale.org/mailing-lists.shtml for more info. Problems
>> should be  sent to listmaster at ale dot org.
>> >> >
>> >>
>> >>
>> >>
>> >> ---
>> >> This message has been sent through the ALE general discussion list.
>> See http://www.ale.org/mailing-lists.shtml for more info. Problems
>> should be  sent to listmaster at ale dot org.
>> >>
>> >
>> >
>> >
>> > ---
>> > This message has been sent through the ALE general discussion list.
>> See http://www.ale.org/mailing-lists.shtml for more info. Problems
>> should be
>> >  sent to listmaster at ale dot org.
>>
>>
>>
>>
>> ---
>> This message has been sent through the ALE general discussion list.
>> See http://www.ale.org/mailing-lists.shtml for more info. Problems
>> should be  sent to listmaster at ale dot org.
> --
> James P. Kinney III   \Changing the mobile computing world/
> President and CEO      \          one Linux user         /
> Local Net Solutions,LLC \           at a time.          /
> 770-493-8244             \.___________________________./
>
> GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
> <jkinney at localnetsolutions.com>
> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7




---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.