Howdy. Your problem isn't about compiling, its permissions. cd
to one level higher than your majordomo directory.
cd /usr/local/majordomo-1.94.4
cd ..
pwd
From there su to root and chmod/own your majordomo directory.
chmod 751 majordomo-1.94.4
chown -R majordomo.daemon majordomo-1.94.4
chown root.daemon majordomo-1.94.4/wrapper
Don't forget that wrapper needs to be owned by root. I don't
think you need a majordomo group, instead majordomo uses the daemon group.
After that, the only other thing that I think you need to fix is your
$whereami variable in your majordomo.cf file.
If anybody spots anything wrong here, please feel free to correct.
What tipped me off to the permissions was the output of the test_config.
See the output that I left below and I think you'll see the problem too.
Let me know if this works to fix your problem though. --Sean
------------------------------
DataCurrent Corp.
ListMail@DataCurrent.Com
<http://www.datacurrent.com>
------------------------------
> ---------------------- list directory ----------------------
> Hmmm, list directory
> usr/test/majordomo-1.94.4/lists doesn't exist
> or isn't a directory.
> Let me try to make it for you...
> BAD: Couldn't create
> usr/test/majordomo-1.94.4/lists, No such file or directory
> --------------------------- log ---------------------------
> Logfile
> usr/test/majordomo-1.94.4/Log didn't exist, trying to create...
> BAD: Couldn't create logfile
> usr/test/majordomo-1.94.4/Log, No such file or directory
>
> BAD: logfile
> usr/test/majordomo-1.94.4/Log exists, but is not writeable or isn't a file.
> ------------------------- Mailers -------------------------
>
> Have you configured where Majordomo is?
> $whereami is goat.up.nic.in
> Good: yup!
> ----------------------- end of tests -----------------------
Follow-Ups:
References:
|
|
