Valdis,
You were correct about the go.user that's why I was getting the: > ./go:
datacom-equipment.com: command not found error but I still can not find
anything wrong anywhere as to why I am getting these bounces and it is
driving me crazy. I have checked every log and they are not appearing in the
logs and I have did a plain old ./go not in the bg so I could se if it was
getting any messages and it isn't. This is all I get as a return e-mail from
my outgoing mail server:
Hi. This is the qmail-send program at smtpd.ha-net.ptd.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
Your message did not reach its destination. Please call your tech support
for assistance. PenTeleData can be reached at 1-800-804-5783. Please
double check the section Bounced <[log in to unmask]> for possible errors and
the following lines to determine cause of this bounce message.
<[log in to unmask]>:
64.40.108.103 does not like recipient.
Remote host said: 553 <[log in to unmask]>... No such
user here
Giving up on 64.40.108.103.
--- Below this line is a copy of the message.
Return-Path: <[log in to unmask]>
Received: (qmail 19828 invoked by uid 50005); 8 Oct 2001 21:48:47 -0000
Received: from [log in to unmask] by smtpd with qmail-scanner-1.00 (uvscan:
v4.1.40/v4164. . Clean. Processed in 1.290755 secs); 08 Oct 2001
21:48:47 -0000
Received: from dr035060.cable-dr.spa.ptd.net (HELO Mike) ([24.229.35.60])
(envelope-sender <[log in to unmask]>)
by smtpd.ha-net.ptd.net (qmail-ldap-1.03) with SMTP
for <[log in to unmask]>; 8 Oct 2001
21:48:45 -0000
From: "Michael Sailer" <[log in to unmask]>
To: "datacom" <[log in to unmask]>
Subject:
Date: Mon, 8 Oct 2001 17:49:55 -0400
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
thanks
-----Original Message-----
From: LISTSERV give-and-take forum
[mailto:[log in to unmask]]On Behalf Of Valdis Kletnieks
Sent: Monday, October 08, 2001 4:51 PM
To: [log in to unmask]
Subject: Re: go.user
On Mon, 08 Oct 2001 15:44:41 EDT, Mike <[log in to unmask]> said:
> [admin@www listserv]$ ./go bg
> ./go: datacom-equipment.com: command not found
I'll bet you have:
NODE= datacom-equipment.com
instead of
NODE="datacom-equipment.com"
The second sets the variable $NODE to the quoted value, the first runs
the command datacom-equipment.com with the variable $NODE set to null.
> 64.40.108.103 does not like recipient.
> Remote host said: 553 <[log in to unmask]>... No such
> user here
And did the syslog on 64.40.108.103 have anything to say about it?
It certainly smells like a /etc/aliases issue to me. Incidentally,
I checked the Sendmail 8.9.3, 8.11.2 through 8.11.4, 8.12.0, and 8.12.1
source trees, and the only reference to THAT error is in the 'cf/README'
file:
virtusertable A domain-specific form of aliasing, allowing multiple
virtual domains to be hosted on one machine. For example,
if the virtuser table contained:
[log in to unmask] foo-info
[log in to unmask] bar-info
[log in to unmask] error:nouser No such user here
[log in to unmask] error:5.7.0:unavailable Address
invalid
@baz.org [log in to unmask]
So 'No such user here' is a locally generated error. I'd check your various
mailertables, virtusertables, and so on, and also check for local rulesets
in the sendmail.mc and sendmail.cf files.
Most likely, sendmail isn't seeing any updates that you think you're
making to /etc/aliases. Possible causes include:
1) The file you updated isn't listed in the 'O AliasFile' line of
sendmail.cf
One possible cause is having *two* AliasFile entries like this:
O AliasFile=/etc/aliases
O AliasFile=/etc/aliases.listserv
when it SHOULD be:
O AliasFile=/etc/aliases,/etc/aliases.listserv
2) You forgot to run 'newaliases' after updating, or it didn't run
correctly,
or similar. Compare the output of 'newaliases' to make sure that both the
files listed and number of aliases per file agree with what you expected.
3) There's something squirrelly in the file.
/Valdis
|
