Jim Hall wrote:
>The mailing list is managed through SourceForge, so it will depend if
>SourceForge provides such an ability to tweak the list. I'll check
>into this.
Thanks for looking into this problem.
>I think I'm confused about how SourceForge has implemented MailMan, or
>else their digest operation isn't working as advertised. I suspect the
>second one.
>
>I checked each of the lists you mentioned (user, devel, kernel) and
>each is set up the same:
>
>- Can list members choose to receive list traffic bunched in digests? YES
>- How big in Kb should a digest be before it gets sent out? 30
>- Should a digest be dispatched daily when the size threshold isn't
reached? YES
That looks correct.
>The last one is the important one, here. The digest *should* be sent
>out on a daily basis, even if the digest hasn't reached 30kb in size.
>So I don't know why it isn't doing that.
Agreed.
>I've resubmitted these settings as "new changes" to see if that forces
>things. Let me know if it does/doesn't work. If it still doesn't work,
>I can open a support ticket with SF.
This didn't seem to change any of this list's behavior. But the
next change did - but maybe not in a useful way. See the following.
>Something else I thought I'd try. I've modified this other setting:
>- How often should a new digest volume be started? MONTHLY
>
>I set it to DAILY for each of the 3 lists you mentioned.
Based on the timestamps, this last change triggered a digest to
be sent. And, if I'm reading the timestamps correctly, that
digest's timestamp was only a few seconds after the timestamp on
your last msg in this digest. Here's the data:
Here's part of this latest digest's header:
>Subject: Freedos-devel Digest, Vol 19, Issue 1
>Date: Mon, 12 Nov 2007 08:21:51 -0800
And here's part of the header from your last msg (which was also the
last msg in this digest):
>Message: 7
>Date: Mon, 12 Nov 2007 10:21:47 -0600
>From: "Jim Hall" <snip>
>Subject: Re: [Freedos-devel] mailing list digest behavior
And, FWIW, here are parts of the headers from your two preceding
msgs. Note that "Message: 6" occurred about 3 minutes before
this digest was created. Maybe that means that the changes you
made prior to posting "Message: 6" did *not* trigger the digest's
creation?
>Message: 5
>Date: Sun, 11 Nov 2007 10:45:55 -0600
>From: "Jim Hall" <>
>Subject: [Freedos-devel] mailing list digest behavior
>Message: 6
>Date: Mon, 12 Nov 2007 10:18:43 -0600
>From: "Jim Hall" <>
>Subject: Re: [Freedos-devel] mailing list digest behavior
I also noticed that the digest processor *did* increment the
"Volume" counter from 18 to 19. That might be temporarily useful -
as an indication that at least some changes to the settings are
getting through. But I feel that, after this problem is solved, the
old setting ("Volume" increments at the beginning of the month) is
preferable.
And here's a few more data points:
1) As of about 11:30 GMT 11/13, I have not received any more digests
from any of those 3 lists.
2) The last digest that I received from the kernel list was Vol 9,
Issue 2 on Oct 28.
3) The last digest that I received from the user list was Vol 17,
Issue 10 on Oct 29.
4) While it is possible that mail delivery problems could cause me
to miss a digest, the fact that the devel digests are getting
through suggests that that part of the system is working OK.
Thanks again for your help on this.
-Eddie
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
