Add support for digest_size_threshold = 0

Bug #558274 reported by mherdeg
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNU Mailman
Status tracked in 3.0
Fix Released
Mark Sapiro

Bug Description

This patch results in no more than one digest being sent per day if digest_size_threshold is set to zero.

This behavior is documented at
"Set this variable to zero to specify that there is no size threshold, in which case no more than one digest will be sent out per day." does not currently implement this behavior. Under the current code, a threshold of zero will always be exceeded, so digest mode will not result in any reduction of traffic for recipients (and will in fact increase message size.) This patch expands the test to check the zero case.

Tags: mailman3

Related branches

Revision history for this message
mherdeg (mherdeg) wrote :

The file was added: rcsdiff output on

Revision history for this message
Jeff White (jwhite530) wrote :

I just ran into this bug as well. This could be resolved by changing something like the attached patch. I see tests/ sets mlist.digest_size_threshhold to zero in test_send_a_digest() so this may break that if it relies on the current incorrect behavior.

Revision history for this message
Mark Sapiro (msapiro) wrote :

The referenced documentation has been changed to reflect current behavior. The admin help for digest_size_threshhold never said that 0 meant unlimited, so I'm marking this as "wishlist" for the moment, but targeting implementation for 2.1.16.

Changed in mailman:
assignee: nobody → Mark Sapiro (msapiro)
importance: Undecided → Wishlist
milestone: none → 2.1.16
status: New → Confirmed
Mark Sapiro (msapiro)
Changed in mailman:
status: Confirmed → Fix Committed
Revision history for this message
Barry Warsaw (barry) wrote :

Adding a MM3 bug task since this seems like it might be interesting for Mailman 3.

tags: added: mailman3
Revision history for this message
Abhilash Raj (raj-abhilash1) wrote :

This bug has been moved to the new gitlab repo here:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.