On Fri, 05 Oct 2001 11:13:31 EDT, Michael Sailer <[log in to unmask]> said:
> I can not however send mail to the list. The list name is
> [log in to unmask] When I send an e-mail to the list I
> get a delivery failure, "unknown user" message from my outgoing mail server.
> My first thought would be the aliases file of which a copy is located below,
> however that seems to be correct. I did also do a newaliases command to make
> sure that it took after the additions were made.
Look at the output of 'newaliases' *carefully*. On my Listserv box,
I get this:
# newaliases
/etc/aliases-lsv-global: 90198 aliases, longest 79 bytes, 4706945 bytes total
/etc/aliases: 4 aliases, longest 28 bytes, 102 bytes total
/etc/aliases-lsv-local: 22298 aliases, longest 77 bytes, 1497196 bytes total
#
Things to check:
1) That the files listed are the files your sendmail.cf is supposed to
be using (most often, this is caused by confusion as to whether the
file name is /etc/aliases or /etc/mail/aliases). In my sendmail.mc
for listserv, I have:
define(`ALIAS_FILE',`/etc/aliases,/etc/aliases-lsv-local,/etc/aliases-ls
v-global')dnl
Which results in a sendmail.cf line of:
# location of alias file
O AliasFile=/etc/aliases,/etc/aliases-lsv-local,/etc/aliases-lsv-global
2) check the number of aliases against the number you expect to have.
I have 22,000 local aliases because I have 5 aliases per list, and
just under 4,500 lists.
3) Look in your syslog output, and see if Sendmail actually sent the mail
to lsv-amin. Here's one (slightly sanitized) set of msgs from this morning:
Oct 5 00:00:36 listserv sendmail[75250]: f9540Zmm075250: from=<[log in to unmask]>, size=304, class=0, nrcpts=1, msgid=<001501c14d53$13a52960$727c52c6@hubby>, proto=ESMTP, daemon=MTA, relay=IDENT:[log in to unmask] [198.82.161.183]
Oct 5 00:00:36 listserv sendmail[63312]: f9540Zmm075250: f9540amm063312: clone: owner=owner-LISTNAME
Oct 5 00:00:36 listserv sendmail[63312]: f9540amm063312: to="|/usr/local/bin/lsv_amin -t LISTNAME", ctladdr=<[log in to unmask]> (1/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=30321, dsn=2.0.0, stat=Sent
If you find 'stat=Sent', then lsv_amin got invoked and wrote it where it
thinks it should go. If you don't have stat=Sent, something is broken.
See (4) and (5) for most common breakages.
4) Make sure that lsv_amin is using the same value of $LSVSPOOL as Listserv.
For the 'lsv' process, it's set in the go.sys script and possibly over-ridden
in go.user. 'strings -a lsv_amin | grep /' should tell you what lsv_amin
uses for its value.
5) lsv_amin should have the correct permissions:
% ls -l /usr/local/bin/lsv_amin
-rwsr-xr-x 1 listserv listserv 25800 Jul 18 2000 /usr/local/bin/lsv_amin
Note that it's set-UID to listserv so it can write in the 'spool' directory.
Failing to run it set-UID will cause bad karma... ;)
/Valdis
|
