Dear everybody,
thanks a lot for all your answers, I've gathered them below
with a little sentence for each.
It must be said that despite I followed all your suggestions
the problem persist sadly!
Any other idea?
Thank you again,
Alberto.
--------------------------------------------------------------
Michael bruns@linmbr.mpae.gwdg.de wrote:
>I solved the problem with the following file permissions
>-rw-rw---- 1 majordom majordom 2562 Jul 9 12:08 test_archive
>for the archive and an additional entry in /etc/group so
>that daemon belongs to the majordom group.
majordom::16:alberto,daemon
did not sesolved the problem (alberto is the list(s) owner)
--------------------------------------------------------------
James byrnejb@harte-lyne.ca wrote:
>Have you added the full archive path to the special @archive variable at
>the bottom of the majordomo.cf file?
I think this must be done only for get-index stuff.
What I'm talking about (excuse me if I repet myself)
is the whole archive file in which is tailored al the mail traffic.
--------------------------------------------------------------
Jimmy pendley@imperial.cc.ca.us
> check the wrapper permission to be sure it is 4755(posix) type, I
forget
>what it should be for non-posix. It should have the "s" in the permission
>for SUID. It should be owned by root and group majordom( or what you named
>the group).
> If that's not it, Let me know and we can go from there. The above is
>probably on the list at least once a month and is the most common error.
-rwsr-xr-x 1 root majordom 6416 Jul 5 18:59 wrapper
I think this is ok.
By the way I recall that this was the key (chmod 4755 + root.majordom)
to solve my "Out of memory!" message.
--------------------------------------------------------------
Dale dale@ns1.chatham.org wrote:
>It looks like majordomo is not set uid properly. Check the faqs and
>readmes as well as the Makefile install: stanza.
done. I seems it's all right.
--------------------------------------------------------------
end of mail! :-)
|
|
