Following up on my previous post, the digest.send script is just a skeleton
of it's purpose. Did you edit the script to match your environment? Any
place there is a "/path/to/" needs to be replaced with the actual path on
your system to wrapper. The digest.send itself needs to be moved/copied
to this same directory. DIGESTDIR=/usr/spool/digests also needs to be
edited to the correct location of your $digest_work_dir (defined in majordomo.cf)
directory, and the script ASSuMEs your digest outgoing alias is
list-digest-outgoing.
The example cron files in the digest.resend should work just fine, again
with all the /path/to references changed to real values.
If you looked at the list-owner-info file, the mkdigest command when emailed
to majordomo with the proper syntax can also be cron'd. To send out daily;
0 4 * * * echo mkdigest list-digest list-digest-outgoing list.passwd | mail majordomo@your.domain
The shortcoming of the above crontab entry, is that you do not want it to go
out from root (postmaster) or majordomo. Majordomo will abort with something
like not replying to myself errors. The other gotcha, is to edit line 605 of
majordomo.pl if you get <name> is not a valid return address error from sendmail.
Try setting sendmail to "always_add_domain" before editing majordomo.pl though.
If you do edit line 605, this is the replacement I use;
# if (!(/\@/ && /\./)) {
if (/\@/ && ! /\./) {
Dan Liston
Caveat: My suggestions are known to work on my systems. You take the risk
and blame|credit for trying them on your systems.
bitter1@absinthe.nu wrote:
>
> Hello; I have a Red Hat Linux 6.2 server and am trying to finish my setup
> of Majordomo 1.94.5. I am new to Linux and its cousins, having been a
> Macintosh person for many years. Apologies if my problem betrays my
> relative inexperience, but I have gone through the FAQ, and through at
> least three books with sections on majordomo... and have nearly given up
> in frustration.
>
> Everything is working except timed digests. They never ever send out.
> Oddly enough, digests which are sent out after a quantity of text is
> accumulated appear to work fine.
>
> I am perplexed. I've fiddled with cron. I've tried altering various
> options on the main and digest configuration file. I've tried every
> imaginable variation of digest aliases.
>
> I suspect three oddities might give a clue.
>
> The "mkdigest [listname] [password]" command does not give an error, but
> does not send out the digest either.
>
> When I attempt to run the "digest" script from the shell I get the
> following error: "Can't locate config_parse.pl in @INC (@INC contains: /
> usr/lib/perl5/5.00503/i386
> -linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /
> usr/lib
> /perl5/site_perl/5.005 .) at digest line 413." However, config_parse.pl
> is right there in the defined Majordomo home directory.
>
> When I attempt to run the "digest.send" script in the Tools subdirectory,
> it gives me this "digest.send: cd: /usr/spool/digests: No such file or
> directory". This directory in fact does not exist, but it was not created
> during the Majordomo installation... and I do not see where it is
> specified in any installation or configuration component. I wonder if it
> is trying to reach the working directory for the digests, which was
> defined at a different location. If so, I am confused why this script
> does not "know" it's looking in the wrong place.
>
> Any assistance onlist or offlist would be eternally appreciated. Thank you.
References:
|
|
