* Omar Thameen (firstname.lastname@example.org) [990912 23:42]:
> On Sun, Sep 12, 1999 at 01:17:24PM +0100, Mats Dufberg wrote:
> > On Thu, 9 Sep 1999 email@example.com wrote:
> > > ----- Transcript of session follows -----
> > > 550 ":incude:/usr/home/majordomo/lists/merlinux"... User unknown
> > (...)
> > > merlinux-list: ":incude:/usr/home/majordomo/lists/merlinux"
> > Try without '"'.
> Or try spelling "include" correctly.
Ha! That's a good one, Omar, nice catch!
I just figured it was a premission thing, it always is (almost anyway).
I have found something very interesting, when majordomo writes new files it uses
umask to do so, but it does not use the mdom or majordomo user's umask setting.
It uses the setting in the majordomo.cf file "config_umask". Well, after
playing with it all weekend I found the variable in majordomo but could not find
where it was being set. I grepped everything, then I realized that the only
thing left was the cf file.
In closing, if you find majordomo saves archive files with 660 permissions
(-wr-wr---) or if mj_build_aliases writes new aliase and config files and sets
them to group writable, it's all over. To correct the problem, change the line
in your majordomo.cf ' $config_umask = 007; ' to 027 (644), this is good if you
want web access directly to your archives.
That is all, enjoy!
Derek E. Mart - Systems Programmer II
U of L - Electrical & Computer Engineering
Pgr: 478-9607 Office: 852-6324
Join S+LUG - www.slug.louisville.edu
PGP Key Fingerprint = AA C4 72 14 97 6F 14 14 B3 9C BB 6E D8 71 9A 67
Description: PGP signature