Sounds more like somebody upgraded sendmail...
Make sure /var/lib/majordomo/lists/mentor exists.
Make sure /etc/aliases is owned by root and only
writable by the owner.
Make sure /, /usr, /var, /usr/lib, and /var/lib
are not group or world writable.
Make sure /usr/lib/majordomo and /var/lib/majordomo
are not group or world writable.
Make sure you have a link to /usr/lib/majordomo/wrapper
in your /etc/smrsh (or equivalent) directory.
This link should be owned by root.
Do an `ls -lR /var/lib/majordomo` and make sure none
of the files or directories are group or world writable,
and that they are all owned by majordomo.
Do the same for /usr/lib/majordomo. The only exception
is that wrapper should be owned by and suid root.
If all of the file and directory permission and ownership
is correct, you really hosed up your /etc/aliases file.
Revert back to your pre-edit copy and see if the problem
goes away.
If you don't have a backup copy of /etc/aliases, pray
for a miracle that you are not discovered as the cause
of the problem. Sorry, just joking. Examine your
aliases file very closely. Look for any line wraps
that are not actually wrapped from the previous line.
Look for aliases that have white space in column 1.
Look for aliases that do not have a : or a closing ".
Dan Liston
Chris Lehmann wrote:
>
> So... majordomo was working just fine, we've got a ton of lists on our
> machine, and then...
>
> I made a change in my /etc/aliases file... *NOT* to any
> list-serv, I ran newaliases and now I get this error any time I try to
> post a message to a list-serv:
>
> 550 5.2.4 :include:/var/lib/majordomo/lists/mentor... Cannot open
> /var/lib/majordomo/lists/mentor: Permission denied
>
> I've tried it in /var/lib... in /usr/lib... everything has group writeable
> permissions turned off... I don't get it.
>
> Help!
>
> -- Chris
> --
> "From what we get, we can make a living, what we give, makes a life"
> -- Arthur Ashe.
References:
|
|
