[38870] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: aol rejects mailing lists?

daemon@ATHENA.MIT.EDU (J.F. Noonan)
Thu Jun 21 00:12:41 2001

Date: Wed, 20 Jun 2001 22:22:17 -0500 (CDT)
From: "J.F. Noonan" <jfn@msc.com>
To: Andy Bradford <bradipo@xmission.com>
Cc: Christian Kuhtz <ck@arch.bellsouth.net>, <nanog@nanog.org>
In-Reply-To: <200106210040.SAA24411@sicilia.bradfordfamily.org>
Message-ID: <Pine.BSI.4.33.0106202213020.13311-100000@pcjfn.msc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu


On Wed, 20 Jun 2001, Andy Bradford wrote:
>
> Hmm, that shouldn't come as a surprise since it isn't even
> listed as an MX:
>
> [andy@home:mail andy]$ dnsmx aol.com
> 15 mailin-01.mx.aol.com
> 15 mailin-02.mx.aol.com
> 15 mailin-03.mx.aol.com
> 15 mailin-04.mx.aol.com
>
> In addition, unless you have some special routes, I'm not even sure how
> you are getting anywhere with that name:
>
> [andy@home:mail andy]$ dnsip air-yh04.mail.aol.com
> 172.18.147.41
>
> Which is clearly a private class address as defined by RFC
> 1918.  Probably a big no-no publishing private addresses in
> your public DNS, but this is AOL we're talking about, right?
> :-)


Arrgh! <self-lart>

<sheepish>
I grabbed the address out of the transaction log and tried it
without really thinking about it.  No, it's not really a surprise
as I filter 1918 addresses at my border.
</sheepish>

Anyway, someone else posted to that list containing the two AOL
addresses three hours ago, and I just sent one myself, and I've
had no bounces from either post yet.  Maybe it was just passing
brain damage, now healed.


--

Joseph F. Noonan
Systems Manager
Rigaku/MSC
jfn@msc.com
http://www.RigakuMSC.com/




home help back first fref pref prev next nref lref last post