LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Valdis Kletnieks <[log in to unmask]>
Mon, 8 Oct 2001 16:51:21 -0400
text/plain (60 lines)
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

ATOM RSS1 RSS2