Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

450 Host down (verizon.net)

34 views
Skip to first unread message

Peter Jam

unread,
Dec 20, 2004, 1:46:48 PM12/20/04
to
Is anyone else having problems with sending to verizon.net
We have several customers and Salses Representatives with verizon.net
addresses. Mail to them doesn't go through and usually doesn't come
back.
I called Verizon IT group, they said they get several calls a week
about this problem, but didn't have a clue. They suggested I send an
e-mail to secu...@verizon.net (No telephone numbers given out for
these folks??)
this was the result of that e-mail:

The attached file had the following undeliverable recipient(s):
secu...@verizon.net

Transcript of session follows:
Command: verizon.net
Response: 450 Host down (verizon.net)

We have 2 DSL accounts with them, but don't use their e-mail. I am
seriously considering not using DSL also!


All ideas or links welcome. Even from verizon.net!

Peter

Ted Kumsher

unread,
Dec 21, 2004, 11:13:22 AM12/21/04
to
Does it NEVER go through or is it intermittent?

What GW/NW versions? Make sure you're patched to latest updates. Note that
if you have NW 5.1, do NOT put any TCPIP updates after SP7.

Check the DNS servers that your GW box is using and make sure it's resolving
the MX records for verizon.net correctly (it shoud get MX record =
relay.verizon.net = 206.46.170.12, UNLESS your DSL connection needs to use
some other internal IP address).

Ted Kumsher

>>> Peter Jam<pj...@lorch.com> 12/20/2004 12:46:48 PM >>>

Peter Jam

unread,
Dec 21, 2004, 2:25:18 PM12/21/04
to
Ted:
Does it consitantly.
Just patched to GW6.5SP3 on NW6.0SP4 but it was doing it with GW6.5SP0
also. I though patch might do something. MX records in DNS are
correct.


We are not a relay, but ATT.net is also blocking us. We do get
responses back from them, see below:

relay=gateway1.att.net[204.127.134.23], delay=1696, status=deferred
(host gateway1.att.net[204.127.134.23] refused to talk to me: 550
unauthorized interface for 162.83.13.215 on mtiwmxc11)


Ted Kumsher

unread,
Dec 22, 2004, 12:11:13 PM12/22/04
to
450 host down means it's unable to connect to their email host. Try a
manual telnet to relay.verizon.net 25.

You could manually add their ip address to route.cfg just to bypass any
possible dns problems. Also, increase your logging level to see if you get
any better log entries.

I'm not familiar with the att.net log you show.

Ted Kumsher

>>> Peter Jam<pj...@lorch.com> 12/21/2004 1:25:18 PM >>>

Peter Jam

unread,
Dec 23, 2004, 10:49:41 AM12/23/04
to
Ted:
Telnet to relay.verizon.net:25:

220 sc004pub.verizon.net MailPass SMTP server v1.1.1 - 121803235448JY
ready Thu,
23 Dec 2004 09:47:49 -0600

That looks good, I think?

Ted Kumsher

unread,
Dec 24, 2004, 10:11:09 AM12/24/04
to
Yep, that looks good. Now you need to figure out if your GWIA server can
resolv and connect. I think there's a tel.nlm someplace . . . I would also
try to setup your route.cfg and see if bypassing dns makes it work.

Ted

>>> Peter Jam<pj...@lorch.com> 12/23/04 9:49 AM >>>

Peter Jam

unread,
Dec 27, 2004, 10:46:16 AM12/27/04
to
Ted:
I think Verizon.net fixed whatever it was that was absobing our
e-mails, because they are going through now??
Never did gert a response from anyone.
0 new messages