Hi Anthony,
Comments inline, and copied to majordomo-users list.
Anthony Gonzalez wrote:
>
> Daniel,
> Good morning!
>
> Hi. Hope you can can help. We are running Majordomo version 1.94.4.
> We have been trying to set up a digest list. We have read the O'Reilly
> book on "Mailing Lists" and we have read numerous articles about how to
> set up a digest. After attempting everything, our digest is not
> working.
> Here's what we have done. Any help would be greatly appreciated!!!
>
> 1. We created two lists: oes2-test and oes2-test-digest following
> normal procedures for a new mailing list.
Some detail in this area would clarify things for me. "Normal" is
very vague. What I consider "normal" is to login or su to the
majordomo account, go to the lists directory, and touch oes2-test
and oes2-test-digest. Then create aliases. More on this under
item #2.
>
> 2. We modified our aliases file to look as follows:
>
> oes2-test: "|/usr/local/majordomo/wrapper resend -s -l oes2-test -f oes2-test-owner -h fiu.edu oes2-test-list"
Forget the "-s", "-f oes2-test-owner", and "-h fiu.edu" in the
alias above and set them in the oes2-test.config file. Here are
the equivalent settings;
administrivia = yes
sender = oes2-test-owner
resend_host = fiu.edu
> oes2-test-list: :include:/usr/local/majordomo/lists/oes2-test, "|/usr/local/majordomo/wrapper digest -r -C -l oes2-test-digest
> oes2-test-digest-list"
Two things here,
1. Digests have a dependency on archives.
2. Utilizing the power of aliases can make lines more readable.
example;
oes2-test-list: :include:/usr/local/majordomo/lists/oes2-test,oes2-test-archiver,oes2-test-digestify
oes2-test-archiver: "|/usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archives/oes2-test/oes2-test -a -M"
oes2-test-digestify: "|/usr/local/majordomo/wrapper digest -r -C -l oes2-test-digest oes2-test-digest-list"
You are/were missing the archiver portion.
The archiver alias has a dependency on the following settings in majordomo.cf
$homedir = "/usr/local/majordomo";
$filedir = "$homedir/archives";
$filedir_suffix = "";
Subdirectories of the above must be created named oes2-test and oes2-test-digest.
Comments on creating directories and setting permissions in item #4
The digestify alias has a dependency on these majordomo.cf settings
$digest_work_dir = "/usr/local/majordomo/digests";
A subdirectory of the above must be created named oes2-test-digest.
Comments on creating directories and setting permissions in item #4
> owner-oes2-test: mariam@fiu.edu
> oes2-test-owner: owner-oes2-test
> oes2-test-request: "|/usr/local/majordomo/wrapper majordomo -l oes2-test"
Above has a dependency on "$majordomo_request = 1;" in /etc/majordomo.cf
> oes2-test-approval: owner-oes2-test
>
> oes2-test-digest: oes2-test
> oes2-test-digest-list: :include:/usr/local/majordomo/lists/oes2-test-digest
> owner-oes2-test-digest: owner-oes2-test
> oes2-test-digest-owner: owner-oes2-test
> oes2-test-digest-request: "|/usr/local/majordomo/wrapper majordomo -l oes2-test-digest"
Above has a dependency on "$majordomo_request = 1;" in /etc/majordomo.cf
> oes2-test-digest-approval: owner-oes2-test
>
> 3. We looked in our majordomo.cf file for the imporant variables and
> their definitions and found the following:
>
> $digest_work_dir = "/usr/local/mail/digest"
See note above... I recommend keeping this in the majordomo $HOME
directory heirarchy.
$digest_work_dir = "/usr/local/majordomo/digests";
> $filedir = "$listdir"
> $listdir = "$homedir/lists"
> $homedir = "/usr/local/majordomo"
> $filedir_suffix = ".archive"
The rest of this is good. Make sure the lines end in ";"
Make sure all directories are owned by majordomo and they
are writable by majordomo, but nobody else. And make sure
your aliases reflect these locations.
>
> 4. We then created the following directories:
>
> /usr/local/mail/digest/oes2-test-digest
> /usr/local/majordomo/lists/oes2-test-digest.archive
>
> They are both owned by "majordomo" and majordomo can write to them.
755 root:root /
755 root:root /usr
755 root:root /usr/local
751 majordom:majordom /usr/local/majordomo
750 majordom:majordom /usr/local/majordomo/archives
751 majordom:majordom /usr/local/majordomo/archives/oes2-test
751 majordom:majordom /usr/local/majordomo/archives/oes2-test-digest
750 majordom:majordom /usr/local/majordomo/digests
755 majordom:majordom /usr/local/majordomo/digests/oes2-test-digest
750 majordom:majordom /usr/local/majordomo/lists
>
> 5. We modified the oes2-test-digest.config file and changed the
> following
> parameters:
>
> digest_issue=1
> digest_volume=1
> digest_maxdays=1
> digest_maxlines=5
> maxlength=2000000
Maxlines seems a bit short, but for testing purposes, ok.
>
> 6. We then attempted to test the digest. I sent a one-line message
> to oes2-test (to which I am not subscribed anymore, but I am subscribed
> to the oes2-test-digest mailing list) and received no e-mail. I then
> attempted
> to send a second e-mail with more than 10 lines, and still get no
> e-mail.
If you have enabled the "restrict_post" setting in oes2-test.config,
make sure it includes oes2-test-digest. Since your digest_work_dir
is not in the majordomo home directory, make sure it is owned and
writable by majordomo. Do the same for subdirectories too. I would
prefer for the sake of troubleshooting, that you follow my examples
above instead though.
>
> 7. When we check in the
> /usr/local/majordomo/lists/oes2-test-digest.archive
> and in the /usr/local/mail/digest/oes2-test-digest directories, we find
> no files.
> (Isn't majordomo supposed to start keeping these files here?)
Not until it actually creates a digest and sends it out. Individual
messages are stored in $digest_work_dir/$list-digest as 001, 002, 003...
Digested messages are stored in
$filedir/$list$filedir_suffix/$list-digest/volume.sequencenumber, probably
/usr/local/majordomo/lists/oes2-test-digest.archive/oes2-test-digest/v01.n001
Then again, I do not archive the digests, I archive the list. The digest
itself creates sort of an archive of it's own like...
/usr/local/majordomo/archives/oes2-test-digest/v01.n001
>
> 8. Also, we are not sure where to go to look at a Log of what is going
> wrong.
> Any ideas where the Majordomo Log is kept? We found a Log file
> in $homedir/Log but it only shows commands that our users are
> sending to Majordomo (like unsubscribes, etc.). We cannot find a log
> showing
> what is going wrong with our digest.
Set "debug = 1;" in majordomo.cf, then look in /tmp for
majordomo.debug and resend.debug files.
>
> 9. We also tried sending majordomo the "mkdigest <list>
> <list-password> command
> but we get this error message back:
This should actually be...
mkdigest <digest> <digest-list> <password>
Majordomo expects your delivery alias to have a -outgoing
suffix to the list name. In your case, oes2-test-digest
would have oes2-test-digest-outgoing instead of what you
have now. (oes2-test-digest-list)
>
> >>>> mkdigest oes2-test [snip]
> mj_digest: ABORT
> Can't create new config file
> /usr/local/majordomo-1.94.4/lists/oes2-test.config
>
The syntax above is incorrect. When you use anything other than
$list-digest-outgoing, you must use the name of the alias your are
sending to in your mkdigest command.
mkdigest oes2-test-digest oes2-test-digest-list <digest-password>
> Why is majordomo trying to create a new config file when that already
> exists?
I am not sure this is really what is happening. Try the
configs and examples I provided and let us (majordomo-users)
know how it worked out.
Dan Liston
|
|
