On 1/7/22 11:04 AM, mm3-omf@sh.werbittewas.de wrote:
debian-dist mailman3 3.3.3-1.
every post to this list will be chunked into one delivery with 60 recipients and one delivery with 21 recipients.
we've searched a bit and found a config-option "max_recipients" for bulk-transfers, but we haven't set it and (as we understand the explaination for this option) then there should be no limit in one transfer to the MTA.
If you haven't set max_recipients, you get the default which is 500. To set it unlimited you set it to 0
nevertheless, we've tried to set it to a high value, but even this doesn't change anything in behaviour.
Right, because chunking isn't arbitrary. Chunking is done by recipient
domain. The addresses are placed in buckets by TLD. All .com goes in
one bucket; .net and .org in another; .edu, .us and .ca in a
third, and all the rest in a fourth.
Then the buckets are chunked with the maximum chunk determined by max_recipients.
In your case, 60 recipients are in one bucket and 21 in another.
The buckets are defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L29 and the work is done at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/bulk.py#L56
My question is why is this important to you? See the FAQ article at https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks about SMTP_MAX_RCPTS which is what max_recipients used to be called) which suggests a much smaller number.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan