RE: _I_couldn't_find_any_host_by_that_name._

[Crow, Ian]

I fixed my problem.

After hours of adding arg and env dumping code to qmail-remote, running many
times, etc. I finally got around to running the same command line as qmailr
as I was running under my standard account.

A comparative strace showed me that the qmailr execution couldn't read
various things in /etc, and hence I discovered that /etc had somehow become
chmod 750-ed. Naturally, this was affecting various other things (like the
locate database update), but they were all further down the list than
getting qmail going.

The thing that compounded my problem was that my standard account is in the
root group, so it wasn't affected by the problem. Any other user and I'd
have nailed the problem much sooner.

My thanks to those who responded.

IanC




This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy the message or disclose its contents to anyone.

RE: _I_couldn't_find_any_host_by_that_name._

[Crow, Ian]

I've had no response at all to my original message, and am still stuck.

My next plan is to uninstall all trace of qmail and reinstall it, but that
seems more like a thing to do with Microsoft OSes than a piece of UNIX
software.

Any really unlikely suggestions I should look at before I do this?

TIA

IanC





This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy the message or disclose its contents to anyone.

_I_couldn't_find_any_host_by_that_name._

[Crow, Ian]

Hello all

I'm having trouble getting mail to send from a Linux box.

I had qmail 1.01 set up to send mail, but wanted to get the SMTP daemon
working. To help me follow instructions relating to inetd I figured I'd
upgrade to 1.03.

I started seeing this when sending a message (and the message never got
sent...):

Mar  6 17:44:47 box qmail: 952364687.681043 delivery 42: deferral:
Sorry,_I_couldn't_find_any_host_by_that_name._(#4.1.2)/

I've been experimenting most of the day, but can't figure out what's wrong.

Here's the setup:
RedHat 5.2
qmail 1.03
Dial-up link to ISP

The following domains, etc are involved:
mydomain.demon.co.uk - A domain with a real MX record
fake-domain.com - A domain we use locally, no DNS server, just hosts
box.fake-domain.com - The Linux server

There's one other thing that might be confusing when looking through the
following. The aim is for the Linux box to send all mail (even for local
users) out to the ISP mail relay, so that its available to them while
they're not in the office. This is why I want mail from
[EMAIL PROTECTED] to [EMAIL PROTECTED] to travel down
the wire, and not simply be routed to a local mail store. I haven't done
anything to influence this behaviour as far as I'm aware, and don't think
this is part of my problem. I'm mentioning it just so it doesn't confuse you
in the following.

If I run qmail-inject -n I get, which looks right:

Return-Path: [EMAIL PROTECTED]
Date: 6 Mar 2000 17:39:07 -
Message-ID: [EMAIL PROTECTED]
From: "My Name" [EMAIL PROTECTED]
to: [EMAIL PROTECTED]

If I drop the -n to qmail-inject so that things really happen I get, which
is not so good:

Mar  6 17:37:57 box qmail: 952364277.225610 new msg 67796
Mar  6 17:37:57 box qmail: 952364277.242731 info msg 67796: bytes 251 from
[EMAIL PROTECTED] qp 2284 uid 500
Mar  6 17:37:57 box qmail: 952364277.377483 starting delivery 39: msg 67796
to remote [EMAIL PROTECTED]
Mar  6 17:37:57 box qmail: 952364277.378444 status: local 0/10 remote 1/20
Mar  6 17:37:57 box qmail: 952364277.420403 delivery 39: deferral:
Sorry,_I_couldn't_find_a_host_by_that_name._(#4.1.2)/
Mar  6 17:37:57 box qmail: 952364277.421614 status: local 0/10 remote 0/20

I tracked down the error message to qmail_remote.c (the sharp eyed will have
noticed I changed 'any' to 'a' in the error message to make sure I'd got the
right spot), and added some code to dump the qmail-remote command line:

argv[0] = qmail-remote
argv[1] = mydomain.demon.co.uk
argv[2] = [EMAIL PROTECTED]
argv[3] = [EMAIL PROTECTED]

I then found that I could invoke qmail-remote directly and successfully send
the message:

/var/qmail/bin/qmail-remote mydomain.demon.co.uk
[EMAIL PROTECTED] [EMAIL PROTECTED]
This is a test
rK194.217.242.92 accepted message.
Remote host said: 250 OK id=12S1TY-000CyR-0Y

So, I'm now completely stumped. My best guess is that something in the
environment of the daemon processes is stopping the name lookup working. Two
things make me think this: a) The error is about name resolution; b) The
dial-up link doesn't fire up, which it does if I do the qmail-remote
directly.

Any ideas anyone?

IanC




This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy the message or disclose its contents to anyone.