On 6/4/23 18:35, Joel Lord wrote:
The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent.
I don't see how that can happen. The process that sends a digest renames
the var/lists/<list-id>/digest.mmdf mailbox file in which the messages
are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf,
where <volume> and <issue> are the volume and issue numbers of that
digest, and then queues a message in the digest queue to tell the
digest runner to create the digest from the messages in that mbox and
send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file
behind and that is created anew when the next post arrives. Further, if
there is a non-empty digest.mmdf file, its messages should be sent no
later than the next 11 PM cron digests.
There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell.
OK
Just to inform things:
(venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1
Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others.
(venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan