Re: Mail to aol.com

James M. Cook ( jcook@interwebb.com )
Mon, 16 Jun 1997 22:15:52 -0400

This is a multi-part message in MIME format.

------=_NextPart_000_01BC7AA2.DA687260
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

But it CAN'T be AOL's fault! This is the perpetual cry from our customers.
Unfortunately, we have a growing number of customers who use their
Internet connection primarily to access AOL so now we're supposed to
support their software as well. :( This access via your ISP method must be
those modem upgrades I keep hearing about in their advertising. Anyway,
that's my $.02
_______________________________________________________________
INTERWEBB COMMUNICATIONS CORP.
James M. Cook - Systems Engineer Tel. (603)798-4477
P.O. Box 4021 FAX: (603)798-4192
30 Chichester Road EMAIL: jcook@interwebb.com
Concord, NH 03302-4021 HTTP://www.interwebb.com

----------
> From: Gregory W. Bondy <gbondy@MAELSTROM.NET>
> To: ntisp@emerald.iea.com
> Subject: Re: Mail to aol.com
> Date: Monday, June 16, 1997 8:15 PM
>
> I am reminded of a line from the Star Trek movie "Undiscovered
Country"...
>
> spock: "But they're dying!"
> kirk: "Let them die."
>
> *climbs onto his soapbox*
>
> It is not the rest of our jobs to "fix" AOL's screwups. It is not for us
> to make elegant workarounds so our users, with whom we all spend a great
> deal of time, money, and effort supporting in the first place, can send
> mail to this den of iniquity that is america online.
>
> *steps off soapbox*
>
> On our system, if mail from AOL bounces, it's sent to /dev/null and
> forgotten about. "Just one of those things". If AOL can't get their
sh*t
> together, and FAST, they'll be a forgotton bad dream in a year. Just
hold
> on. :)
>
> My two cents.
>
> At 05:44 PM 6/16/97 -0600, you wrote:
> >The AOL mail deal used to be a problem with me. I'm not a DNS guru by
any
> >means, but I was told by several that AOL returns truncated DNS entries.

> >What this looks like: I don't know. But I do know that it screwed up my
> >mail for quite a while until an update for my SMTP server came out
> >addressing the AOL issue.
> >
> >QUICK FIX: (Tested and used by me previously: unknown if this will work
> >now). Some SMTP servers have trouble handling AOL's truncated returns.
> >Solution: Create an AOL.COM DNS zone hosted on your own system. Do a
> >dig/nslookup & find some of AOL's lower priority (higher numbered) mail
> >machines, and create a couple MX records in your local AOL.COM zone
> >pointing to those IP addresses. Now you won't have to rely on AOL's
> >screwed up DNS returns. AOL mail lookups will be local on your system.
> >Please don't ask me how to create a new DNS zone on your server - I
won't
> >know what to tell you. Be advised that this will most likely affect
users'
> >ability to visit AOL websites.
> >
> >Eric
> >mailserve@pdqnet.net
> >
> >----------
> >> From: John Lange <microjl@palacenet.net>
> >> To: ntisp@emerald.iea.com
> >> Subject: Re: Mail to aol.com
> >> Date: Monday, June 16, 1997 4:38 PM
> >>
> >> Don't forget the inherent problems caused by their backbone provider
> >> Sprint(missing)Link.
> >>
> >> JOhn :}
> >>
> >> > >Does anyone else have trouble getting mail to aol.com?
> >> >
> >> > we've had all sort of problems with email and web traffic to
aol.com,
> >> > ostensibly because of they high level of traffic they are(n't)
> >> handling...
> >> >
> >> > so far, none of our customers have whined too loudly...
> >> >
> >>
> >> John C. Lange, Sr. PALACE dot NET, INC.
> >> microjl@palacenet.net MICRO-TECH Computers!
> >> 608.742.1601 & 6980 2800 New Pinery Road, Suite 10
> >> http://www.palacenet.net/ Portage, WI 53901
> >> http://www.microt.com/
> >>
> >> --- __o
> >> --- _-\<,_ FASTEST SERVICE IN TOWN
> >> --- (_)/ (_)
> >>
> >> ----------
> >>
> >>
> >>
> >> ----------------------------------------------------------
> >> NTISP Mailing List listserver@emerald.iea.com
> >
> > ----------------------------------------------------------
> > NTISP Mailing List listserver@emerald.iea.com
> >
> >
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
------=_NextPart_000_01BC7AA2.DA687260
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

But it CAN'T be AOL's fault!  This =is the perpetual cry from our customers.  Unfortunately, we have a =growing number of customers who use their Internet connection primarily =to access AOL so now we're supposed to support their software as well. =:( This access via your ISP method must be those modem upgrades I keep =hearing about in their advertising.  Anyway, that's my =$.02
_______________________________________________________________INTERWEBB COMMUNICATIONS CORP.
James M. Cook - Systems Engineer =   Tel. (603)798-4477
P.O. Box 4021 =            &=nbsp;           &n=bsp;           FAX=: (603)798-4192
30 Chichester Road =            &=nbsp;           &n=bsp;  EMAIL: jcook@interwebb.com
Concord, NH 03302-4021 =            &=nbsp;     HTTP://www.interwebb.com


----------
> =From: Gregory W. Bondy <gbondy@MAELSTROM.NET>
> To: ntisp@emerald.iea.com
> Subject: Re: Mail to aol.com
> Date: =Monday, June 16, 1997 8:15 PM
>
> I am reminded of a line =from the Star Trek movie "Undiscovered Country"...
> =
> spock: "But they're dying!"
> kirk: = "Let them die."
>
> *climbs onto his =soapbox*
>
> It is not the rest of our jobs to ="fix" AOL's screwups.  It is not for us
> to make =elegant workarounds so our users, with whom we all spend a great
> =deal of time, money, and effort supporting in the first place, can =send
> mail to this den of iniquity that is america online. = 
>
> *steps off soapbox*
>
> On our =system, if mail from AOL bounces, it's sent to /dev/null and
> =forgotten about.  "Just one of those things".  If =AOL can't get their sh*t
> together, and FAST, they'll be a =forgotton bad dream in a year.  Just hold
> on. :)
> =
> My two cents.
>
> At 05:44 PM 6/16/97 -0600, you =wrote:
> >The AOL mail deal used to be a problem with me. = I'm not a DNS guru by any
> >means, but I was told by =several that AOL returns truncated DNS entries.
> >What this =looks like: I don't know.  But I do know that it screwed up =my
> >mail for quite a while until an update for my SMTP server =came out
> >addressing the AOL issue.  
> =>
> >QUICK FIX: (Tested and used by me previously: unknown =if this will work
> >now).  Some SMTP servers have trouble =handling AOL's truncated returns.
> >Solution: Create an =AOL.COM DNS zone hosted on your own system.  Do a
> =>dig/nslookup & find some of AOL's lower priority (higher =numbered) mail
> >machines, and create a couple MX records in =your local AOL.COM zone
> >pointing to those IP addresses. = Now you won't have to rely on AOL's
> >screwed up DNS =returns.  AOL mail lookups will be local on your system.
> =>Please don't ask me how to create a new DNS zone on your server - I =won't
> >know what to tell you.  Be advised that this will =most likely affect users'
> >ability to visit AOL =websites.
> >
> >Eric
> >mailserve@pdqnet.net
> >
> >----------
> >> =From: John Lange <microjl@palacenet.net>
> >> To: ntisp@emerald.iea.com
> >> Subject: Re: Mail to aol.com
> =>> Date: Monday, June 16, 1997 4:38 PM
> >>
> =>> Don't forget the inherent problems caused by their backbone =provider
> >> Sprint(missing)Link.
> >>
> =>> JOhn :}
> >>  
> >> > >Does =anyone else have trouble getting mail to aol.com?
> >> > =
> >> > we've had all sort of problems with email and web =traffic to aol.com,
> >> > ostensibly because of they =high level of traffic they are(n't)
> >> handling...
> =>> >
> >> > so far, none of our customers have =whined too loudly...
> >> >
> >>
> =>> John C. Lange, Sr. PALACE dot NET, INC.
> =>> microjl@palacenet.net MICRO-TECH Computers!
> >> =608.742.1601 & 6980 2800 New Pinery Road, Suite =10
> >> http://www.palacenet.net/ Portage, WI 53901
> >> http://www.microt.com/
> >>
> >> =      ---    __o
> =>>      ---   _-\<,_ =   FASTEST SERVICE IN TOWN
> >> =      --- (_)/ (_)
> >> =
> >> ----------
> >>
> >>
> =>>
> >> = ----------------------------------------------------------
> =>>  NTISP Mailing List =            &=nbsp;listserver@emerald.iea.com
> >
> > =----------------------------------------------------------
> > =NTISP Mailing List =            &=nbsp;listserver@emerald.iea.com
> >
> >
>
> = ----------------------------------------------------------
> = NTISP Mailing List =            &=nbsp;listserver@emerald.iea.com

------=_NextPart_000_01BC7AA2.DA687260--