Is the config snippet from your rmgroup.config or rmgroup-digest.config?
The second digestify alias is the correct one, as long as your mailing
list is not hosted in a domain the does not match the default in your
current majordomo.cf file. The commented first digestify alias is the
correct one (provided you fix the missing comma typo) when your list or
your majordomo is hosted.
Lastly, what is the "maxlength" setting in the rmgroup-digest.config?
Any time your digest_work_dir files get larger than maxlines or maxlength,
or older than maxdays, a digest is created and sent. Only when a message is
received that when added to the rest of the spool EXCEEDS one of the values
is the digest created.
Hope this helps,
Dana Holland wrote:
> I have one more question about digests. Below is my aliases file for
> one of my lists. You'll notice that I've commented out one of the
> digestify lines. Using the line that is uncommented, this never sends
> out a digest, but I can put a command in the cron to force one every
> night and it works. If I put the other line back in (the one currently
> commented out), it sends out a digest every time someone posts to the
> list. I've also posted a portion of my rmgroup-digest.config file
> below. No matter what I do, I can't seem to change that behavior. The
> way I have it currently set up (forcing a digest every night) is
> bearable, but I wish it would work the other way.
> owner-rmgroup: rmgroup-owner
> rmgroup: "|/usr/local/majordomo-1.94.5/wrapper resend -C
> /usr/local/majordomo-1.94.5/majordomo-1.cf -l rmgroup -h
> dana-holland.com -s rmgroup-outgoing,nobody"
> rmgroup-owner: firstname.lastname@example.org
> rmgroup-request: "|/usr/local/majordomo-1.94.5/wrapper majordomo -l
> rmgroup -C /usr/local/majordomo-1.94.5/majordomo-1.cf"
> rmgroup-approval: owner-rmgroup
> rmgroup-archiver, rmgroup-digestify
> owner-rmgroup-outgoing: owner-rmgroup
> rmgroup-archiver: "|/usr/local/majordomo-1.94.5/wrapper archive2.pl -f
> /usr/local/majordomo-1.94.5/archive/rmgroup -a -M"
> #rmgroup-digestify: "|/usr/local/majordomo-1.94.5/wrapper digest -r -C
> -c /usr/local/majordomo-1.94.5/majordomo-1.cf -l rmgroup-digest
> rmgroup-digestify: "|/usr/local/majordomo-1.94.5/wrapper digest -r -C -l
> rmgroup-digest rmgroup-digest-outgoing,nobody"
> owner-rmgroup-digest: owner-rmgroup
> rmgroup-digest: rmgroup
> rmgroup-digest-owner: rmgroup-owner
> rmgroup-digest-request: "|/usr/local/majordomo-1.94.5/wrapper majordomo
> -C /usr/local/majordomo-1.94.5/majordomo-1.cf -l rmgroup-digest"
> rmgroup-digest-approval: rmgroup-approval
> # digest_issue [integer] (1) <digest>
> # The issue number of the next issue
> digest_issue = 203
> # digest_maxdays [integer] (undef) <digest>
> # automatically generate a new digest when the age of the oldest
> # article in the queue exceeds this number of days.
> digest_maxdays = 1
> # digest_maxlines [integer] (undef) <digest>
> # automatically generate a new digest when the size of the digest
> # exceeds this number of lines.
> digest_maxlines = 999999
> # digest_name [string] (rmgroup-digest) <digest>
> # The subject line for the digest. This string has the volume and
> # issue appended to it.
> digest_name = rmgroup-digest