> I've been looking over some of the digest stuff for the last hour or so,
> and I'm finding myself coming very short on the comprehension end of
> things.
>
> First a simple question:
> Can Majordomo 1.90 provide one digest per day as its own list (i.e. I
> don't want list foo AND foo-digest, I just want foo-digest to be
> available). Sample sendmail aliases that do this are more than welcome.
> Ideally what I'm wanting is a list ``foo'' that is archived and sends
> out one digested message per day to all of the members of the list IF
> there is anything to send out.
lists and digest versions of the same list are completely separate entities
to majordomo. So you can easily set up just the list, just the digest, or
both. They are related in name only.
> Other questions:
> The docs are rather lacking on this topic -- Where do the digests go?
> What happens when? How do they go out once per day when Majordomo isn't
> a daemon keeping track of what time it is? Am I supposed to use cron?
> What exactly _should_ I be doing from cron if that's what I am supposed
> to use (what command)?
As the articles are received, 'digest' puts them in a digest spool directory
($digest_work_dir in majordomo.cf). After each article is placed, digest
decides if a digest should be created, based on the number of bytes in the
message. That's it.
However, I made some enhancements to majordomo that didn't get into 1.90
except as a patch (contrib/digest.diff). Basically, my patch allows you
to specify different critera for making a digest, including a minimum age
of the articles in the queue waiting to be digestified. So for your case,
you could specify the minimum age as zero, and if any articles were waiting
at night, a digest would be created and sent.
You're right that majordomo isn't a daemon keeping track of time, and since
you can't control when you will get messages (and thus when digest would be
run), you run a digest command nightly via cron.
You can try without my patch, and use -m nightly. It will abort if there
are no messages in the queue, which might be annoying, but might work.
> I'm really trying to avoid some huge web of cron scripts + homebrew
> scripts + majordomo to maintain this stuff -- that's why I left listproc
> 6.0c in the first place. Ease of maintenance is key.
A one-line cron job is sufficient. After all, if you want once per day,
cron is the way to do it.
Like this (if you apply my patches):
5 1 * * * /local/majordomo-1.90/wrapper digest -p -C -l foo-digest foo-digest-outgoing
(or use -m instead of -p if you don't). foo-digest-outgoing is typically
just :include:<wherever>/lists/foo-digest, but can include archiving.
> As always, thanks for your time.
You're welcome. Let me know if you have any problems....
--
Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc
No fate but what we make
References:
-
Digests
From: Jeff Blaine <Jeff.Blaine@ciesin.org>
|
|
