Dear Mark,
excellent suggestion, indeed there were messages heavily formatted
which apparently affected mailman and its normal processing of digest
buffer. There was no need to remove these messages. Re-starting the
list server did the miracle and both lists are now working fine,
dispatching the digest-mode messages as intended. Thanks again for
your help. Issue fixed and closed.
regards
Lluis
Quoting Mark Sapiro <m...@msapiro.net>:
Lluis Montoliu wrote:
the two large list are not sending any digest-mode, with the exact
same settings, even if I decrease the value to 256 or if I trigger
sending a new digest dispatch right now, which does not happen. I'm
totally amazed. I've seen the archives of mailman and, unfortunately,
the problems with digest-mode appear to be rather common, many reports
found, but not really solutions, at least, I could not find the one
that will fix my bug.
There is almost certainly a message or messages in the
lists/LISTNAME/digest.mbox files for these lists that is causing an
exception to be thrown in the scrubber in it's attempt to process the
digest.
Ask the hosting provider to look for relevant error messages and
tracebacks in Mailman's error log.
You may have to have the hosting provider just move the
lists/LISTNAME/digest.mbox files aside and abandon the current
accumulated digests if the hosting provider can't do anything more
selective to find and fix the offending messages.
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
