reject on require_explicit_destination max_num_recipients
![](https://secure.gravatar.com/avatar/ac847e3bb1213b500ff8941fb0d145bb.jpg?s=120&d=mm&r=g)
Just to confirm I'm not missing something, am I correct that there is no way (other than patching) in Mailman 2.1.37 to automatically reject posts that trigger the require_explicit_destination or max_num_recipients limits?
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 12/18/21 10:57 AM, Russell Clemings wrote:
You are correct. You would need to patch Mailman/Handlers/Hold.py or, if you wanted to do this in a way that didn't involve patching distributed code, you could create a custom handler (see https://wiki.list.org/x/4030615) to do the rejection and put it in the pipeline before Hold or create a patched version of Hold.py and replace Hold in the pipeline with the modified (and renamed) Hold.py. These latter methods only require adding a file in Mailman/Handlers/ and adding things in mm_cfg.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 12/18/21 10:57 AM, Russell Clemings wrote:
You are correct. You would need to patch Mailman/Handlers/Hold.py or, if you wanted to do this in a way that didn't involve patching distributed code, you could create a custom handler (see https://wiki.list.org/x/4030615) to do the rejection and put it in the pipeline before Hold or create a patched version of Hold.py and replace Hold in the pipeline with the modified (and renamed) Hold.py. These latter methods only require adding a file in Mailman/Handlers/ and adding things in mm_cfg.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Russell Clemings