Matthew Reeve wrote:
>
> I have recently started using majordomo, and while configuring a digest
> version of my list I have come across a perplexing problem. The undigested
> list works properly, and has no problems at all. The undigested list mails
> are added to digests which are made correctly and can be seen when using a
> telnet connection to the server. These can be forced to make using mkdigest
> or happen based on the size restrictions. However, the digests are not being
> sent out to any list members.
Here's how I do it (don't remember who I got this info from, though):
[root@lug /etc/cron.midnight]# cat mkdigest
#!/bin/sh
#
# Script to force digest creation
# Created by Todd A. Lyons <todd@mrball.net> 11/04/00
LOG=/var/log/mj_digest
echo mkdigest cerritoslug-digest merlin.cerritoslug-digest.admin | mail \
majordomo@lug.linxsys.com >> $LOG 2>&1
You then have to create an entry in your /etc/crontab to make the directory
/etc/cron.midnight run every night at midnight (actually 12:01 in my case).
Similar to:
[root@lug /etc]# cat crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# run-parts
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly
01 0 * * * root run-parts /etc/cron.midnight
> Here is the aliases file which I assume is the centre of the problem. It is
> running -
If it's creating the digest, then your aliases are fine.
Blue skies... Todd
--
Most traditional Pee-Cee user groups, I've noticed, function mainly as
commiseration societies for people who've bought lousy hardware, are
struggling and wasting time trying to deal with it, and want to exchange
coping-strategy tips with others in the same boat. -- Rick Moen
References:
|
|
