>Mark Sapiro wrote: >You need the cron job because nothing else in Mailman sends digests >periodically. The only other mechanism sends a digest when the list's >digest.mbox exceeds a certain size, which may not happen for weeks on >a low traffic list.
Ok I understand 100% now. The only reason I kept telling you that I am "pretty sure" people are getting their digests, is because I went to someone's office once and saw that they had some digests in their inbox. And I personally forced one of my own tests lists to get a 30K digest.mbox so I could see what a digest delivery looked like. In looking over my recursive listing closely, I see that there are 501 total digest.mboxes out there (!). All of them are 30K or under. >>That still doesn't explain why they are all still there and nothing was >>delivered when I ran the cron job at 12:48 today... >Are you sure digest_send_periodic is set to Yes for those lists that have >old digest.mbox files? Absolutely. That is the default we set up and I just checked a bunch of lists to verify it. I did check out a couple of the lists that had outstanding digest.mboxes and found that they didn't have any subscribers with the digest option checked (as I said, very few of our users know about and use this feature) so perhaps nothing was delivered today because there was just nothing to be delivered. I take it a digest.mobx is created regardless of whether or not a list has any members using that option. So perhaps everything is fine and starting this daily senddigests cron job will be a seamless transition. Thanks! - jim - ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9