>>Savoy, Jim wrote:
>>Two of them yes, but the other two no.
>Mark Sapiro wrote:
>For the two old ones, be sure to check the list's digest_send_periodic
setting.
Right. That was the difference. They are the only two that say NO to
this query.
Thanks for everything, Mark.
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>Are they for lists that had a post arrive during or immediately after
>>the time the digest was sent? In other words do they just contain
>>messages waiting for the next digest?
>
>Two of them yes, but the other two no. I will deal with this later and
>S
Savoy, Jim wrote:
>
>I think you nailed it. This is different from cron/crontab.in. The
>latest
>changes I made are not reflected. So am I supposed to do the:
>
> cd mailman/cron
> crontab -u mailman crontab.in
>
>every time I make a change to the crontab.in file? I believe that was
>the
>very
Savoy, Jim wrote:
>
>Since we are trying to troubleshoot a very mysterious problem, I should
>include all of the information I have. When I ran senddigest by hand (as
>user mailman), I did get a warning:
>
>[mailman cron]$ ./senddigests
>/mail/mailman/pythonlib/korean/c/euc_kr.py:24: RuntimeWarnin
>>Savoy, Jim wrote:
>>If/when we resolve this, I guess I'll have to start a new thread on
>>why those 3 didn't go away. :-)
>Mark Sapiro wrote:
>Are they for lists that had a post arrive during or immediately after
>the time the digest was sent? In other words do they just contain
>messages wai
Savoy, Jim wrote:
I didn't get anything mailed to me when I added the MAILTO though...
Divide and conquer. First get a dead simple cron job working, maybe one
that runs every few minutes and does something like:
date >> /tmp/foo-cron; echo "done"
Once that is working and you are receivin
>> Jim Savoy wrote:
>>So obviously, this has something to do with this being run from cron.
>>You would think all of it would fail though (the checkdbs stuff runs
>>fine from cron).
Hmmm - the above may not be true. Checkdbs did not run this morning.
Mark Sapiro wrote:
>What does "crontab -u ma
Mark Sapiro wrote:
>Try
>su mailman
>cron/senddigests
Since we are trying to troubleshoot a very mysterious problem, I should
include all of the information I have. When I ran senddigest by hand (as
user mailman), I did get a warning:
[mailman cron]$ ./senddigests
/mail/mailman/pythonlib/kore
Savoy, Jim wrote:
>
>If/when we resolve this, I guess I'll have to start a new thread on
>why those 3 didn't go away. :-)
Are they for lists that had a post arrive during or immediately after
the time the digest was sent? In other words do they just contain
messages waiting for the next digest?
>Mark Sapiro wrote:
Thanks for the MAILTO info.
>Try
>su mailman
>cron/senddigests
Boom. That worked. All (but 3) of the 501 digest.mboxes are gone
now and I got a delivery from the list I am a digest member of.
It ran rather quickly too (1 minute flat).
If/when we resolve this, I guess I'll
Savoy, Jim wrote:
>
>Ran it by cron. I don't see any activity at all when it runs (when I ran
>the checkdbs program, python lead the way when I did a "top", but
>nothing
>seems to happen when I run senddigests).
Try
su mailman
cron/senddigests
It probably won't be any different, but it's worth
>>Jim Savoy wrote:
>>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.
>Mark Sapiro wrote:
>But, assuming this is a more or less standard Mailman (2.1.5), even if
>no one is subscribed
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>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
>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
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>The digest messages are accumulated for a list in a mbox format file
>>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>>digest.mbox and the size of digest.mbox is now greater than the list's
>>digest_size_threshold, a digest is se
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>Running cron/senddigests will send a digest for any list which has a
>>digest.mbox file and for which digest_send_periodic=yes regardless of
>>how big the digest is.
>
>This is where we part ways.
>
>Without the senddigests cron job, isn't the above stat
>Mark Sapiro wrote:
>The digest messages are accumulated for a list in a mbox format file
>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>digest.mbox and the size of digest.mbox is now greater than the list's
>digest_size_threshold, a digest is sent at that time for that
>Mark Sapiro wrote:
>The digest messages are accumulated for a list in a mbox format file
>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>digest.mbox and the size of digest.mbox is now greater than the list's
>digest_size_threshold, a digest is sent at that time for that
Savoy, Jim wrote:
>
>All of our lists allow users to select the
>digest
>
>option ("digestable=yes"), and the digests are sent out when the 30k
>threshold is
>
>reached ("digest_size_threshold=30"). The next option asks if a digest
>should be
>
>sent out DAILY when the threshold isn't reached
>("di
Hi all,
I started a new thread for this as it no longer applies to cron, but
rather digests.
I just ran the senddigests cron option (again, for the first time ever)
but it didn't seem to do anything. I can't really understand what it
does anyway
(from the description given). All of ou
20 matches
Mail list logo
