Anonymous_User Absent Member.
Absent Member.
1363 views

450 Host Down message/between domains

Using Groupwise 6.5 and Novell 6, we can not successfully send email to a
specific domain OUTSIDE of our company. We get the following messages in
the GWIA log:

Detected error on SMTP command
Command : (the intended recipient)
Response: 450 Host Down (the intended recipient)
Deferring message

The recipient's ISP claims to have never received any message. We can
successfully email this recipient using a different email client.

Any ideas?

Fred Jeffers
Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: 450 Host Down message/between domains

fjeffers@ams.fm wrote:
> Using Groupwise 6.5 and Novell 6, we can not successfully send email to a
> specific domain OUTSIDE of our company. We get the following messages in
> the GWIA log:
>
> Detected error on SMTP command
> Command : (the intended recipient)
> Response: 450 Host Down (the intended recipient)
> Deferring message
>
> The recipient's ISP claims to have never received any message. We can
> successfully email this recipient using a different email client.
>
> Any ideas?


This is really a question best posed on the support forums. These forums
are intended for peer support for software developers. However, since
you can provoke the behaviour at will could you use a number of
techniques to investigate it. Given the description I'd guess at DNS
problems first. Start with NSLookup (preferably on your host that does
the SMTP forwarding). Then use the following commands:

SET TYPE=MX
foreign.domain

Replace foreign.domain with the domain name you can't send to, e.g.:

SET TYPE=MX
novell.com

You should see the mail exchanger (MX) record for the domain and the
address (A) record for the mail exchanger. Then switch to a public
server that is external to your own domain/network:

SERVER 137.65.1.1
SET TYPE=MX
foreign.domain

137.65.1.1 is Novell's public DNS server and it will do recursive
lookups for external queries. If the result of the second set of
commands is different from the first then the probable cause is DNS
mis-configuration on your mail forwarder. It could be that it has the
wrong DNS IP or that the DNS server it is using has a stale MX or A
record for the problem domain.

If that doesn't work you could try Ethereal or another packet capture
application to capture frames that target the foreign domain's MX IP
address and simply send it an e-mail. You should capture the SMTP
exchange and the cause might be obvious. Note that you will have to run
the capture program on your mail forwarder or use a hub or configure a
switch port to echo your mail forwarder's switch port.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.