Well, I seem to still have a couple of nagging problems with my li'l box
here, so if you don't mind, I'll pick your brains on this one.
1) For some reason, Majordomo isn't logging anything. Nada. Zilch. The
directory is correct, with correct ownership/permissions/etc. This isn't
really a problem as far as I'm concerned, other than it'd be nice to know
what it's doing/has done. :)
2) Here's the more important of the two. I have a total of about 8
mailing lists set up. They're all working properly as far as I can tell,
including archiving. The stuff is all going to
/tools/majordomo-1.93/archives just like it should. BUT: If you issue
an index command, you get told there aren't any files available. I've
been over and over this, checking and re-checking the directories,
permissions, and even the majordomo.cf to make sure it's got the right
information. the .cf file shows this:
# Majordomo will look for "get" and "index" files related to $list in
# directory "$filedir/$list$filedir_suffix", so set $filedir and
# $filedir_suffix appropriately. For instance, to look in
# /usr/local/mail/files/$list, use:
# $filedir = "/usr/local/mail/files";
# $filedir_suffix = ""; # empty string
# or to look in $listdir/$list.archive, use:
# $filedir = "$listdir";
# $filedir_suffix = ".archive";
$filedir = "/tools/majordomo-1.93/archives";
$filedir_suffix = "";
All of the files, of course, are file.archive9601 (I'm using monthly
archives) and all have read/write permissions allowing Majordomo access
to them as it needs. Can someone perhaps point me in the right direction?
Lists all go to /tools/majordomo-1.93/lists, and while I did notice in
the list.config files a couple of variables asking for archive directory
and what-not, I also noticed these same variables instructed the user to
leave them blank as the feature was not yet working. I've spent quite
a few hours on this now, but seem to be making little headway...
Frustrated, but not giving up yet, dammit! *smile*
TIA,
Michael Young
|
|
