[ TenantNet writes: ]
> I'm perplexed. Our digest seems to be working, but rather than waiting
> until it "fills up" it triggers and gets sent out when it's about 10K in
> size. We're not using mkdigest at this time. In the digest config file, we
> have the options set as:
> digest_maxdays = 1
> digest_maxlines =
> maxlength = 40000
> I know the maxdays would indicate it goes out once a day but that doesn't
> seem to work either. We're not high volume yet and I had a few messages sit
> there for several days, so the maxdays didn't send them out irrespective of
> the size, but when I added a new message to the pile (so to speak) it
> triggered it. The resulting digest was only 9,243 bytes. The 40,000 might
> be high, but it should allow me to decide when to trigger a digest with
> mkdigest, yes?. Or am I missing something.
Since digest_maxdays can't be tested until digest runs, it only works at
the minimum granularity of how often messages are received. Thus for the
values you have set above, if the list went for several days without a
posting, obviously the next posting would trigger a digest by virtue of
the digest_maxdays value, irrespective of the other trigger values. I
think the usual way of ensuring periodic digests is to run digest with
the -p option from cron (plus appropriate -c/-C/-l options).
Also note that "maxdays" is a bit of a misnomer. The actual check is "a
message file exists more than (digest_maxdays * 24) hours old", so if a
message comes in at 10:00 AM today and another at 9:00 AM tomorrow, no
digest is generated because the oldest message is less than 24 hours old
(assuming digest_maxdays=1). What do folks think, should digest coerce
this test to midnight, so that it is more in line with "days" instead of
> If I undefined maxdays, would I then have complete control up to the
Looks like it to me.
> Have I missed any parameters? Does the regular non-digest list (that
> feeds the digest) config file have any bearing on this?
Not if you specified the digest list to the -l option on the digest