Bug 337 - "unqualified hostname unknown" and "unable to qualify my own domainname"
"unqualified hostname unknown" and "unable to qualify my own domainname"
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: sendmail (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-12-07 20:41 EST by walt
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1998-12-10 10:31:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description walt 1998-12-07 20:41:35 EST
I'm running RedHat 5.2, with libc-5.3.12-28.

I'm having problems with sendmail. I used /bin/mail to
try to send messages to "jari_aalto@poboxes.com".
Whenever sendmail processes the queue, it logs messages
like:

Dec  7 20:06:05 orbit sendmail[13764]: My unqualified \
host name (orbit) unknown; sleeping for retry

Dec  7 20:07:05 orbit sendmail[13764]: unable to qualify \
my own domain name (orbit) -- using short name

I'm using the stock sendmail.cf. Other files that might
be of interest are:

/etc/hosts:
127.0.0.1	loopback
0.0.0.0		orbit

/etc/resolv.conf:
domain trytel.com
nameserver 209.167.55.5
nameserver 209.167.55.15
nameserver 207.112.63.4

/etc/nsswitch.conf: (changed lines ONLY)
passwd:     files
shadow:     files
group:      files

hosts:      files dns

I'm using PPP to connect to two ISPs (and plan to add a
third soon). They are "trytel.com" (my primary ISP) and
"wonder.ca". Because I'm connecting to two, I hesitate
to define either one in the $j macro in sendmail.cf
or to specify a smart mail host with DS.

How can I get sendmail to send mail?
Comment 1 Derek Tattersall 1998-12-08 11:46:59 EST
I cannot really tell from the information that you provided, but the
IP address for orbit (0.0.0.0) is what is causing your problem.  This
is not a valid IP address for a machine.  You might want to check
with your ISP to verify that you are using a valid address for orbit.

Note You need to log in before you can comment on or make changes to this bug.