North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: RFC1918 addresses to permit in for VPN? (fwd)

  • From: John Fraizer
  • Date: Sat Dec 30 03:30:28 2000

I've been getting flamed by several of you off-list for picking on a "big
carrier."

As result, I decided to pass this one on to the list.

---
John Fraizer
EnterZone, Inc


---------- Forwarded message ----------
Date: Sat, 30 Dec 2000 02:56:50 -0500 (EST)
From: Wants to keep his job <[email protected]>
To: John Fraizer <[email protected]>
Subject: RE: RFC1918 addresses to permit in for VPN?

Yeah, this "network architect" responded to a post of mine on NANOG that
using TAP to send pages was just dumb when I could simply email my pager
"directly".  Uh...  Yeah, that will get my page about "the internet" being
down right out to my pager right quick.

Of course I didn't see his response for a few weeks, as it fell into my
spam folder.  Wonder why?

[email protected][~]$ telnet 205.152.173.2 25
Trying 205.152.173.2...
Connected to ns1.arch.bellsouth.net.
Escape character is '^]'.
220 ns1.arch.bellsouth.net ESMTP Sendmail 8.9.1a/8.9.1; Sat, 30 Dec 2000
02:53:06 -0500 (EST)
mail from: [email protected]
250 [email protected] Sender ok
rcpt to: [email protected]
250 [email protected] Recipient ok
data
354 Enter mail, end with "." on a line by itself
sigh...

.
250 CAA02152 Message accepted for delivery
quit
221 ns1.arch.bellsouth.net closing connection

enough said.  flame on...

(name deleted)




---


Bellsouth:  Please patch your spam hole.  We all know they'll be using
that one now.

BTW: Any reason why you have SMTP service on a nameserver available from
the global internet

Money that tight that you can't have dedicated boxes to do DNS and DNS
only?

(On the phone to brokers voicemail: "Bellsouth: SELL IT! SELL IT! SELL
IT!")


---
John Fraizer
EnterZone, Inc