Am 07.01.22 um 21:33 schrieb Mark Sapiro:
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
bucketsby TLD. All.comgoes in one bucket;.netand.orgin another;.edu,.usand.cain a third, and all the rest in a fourth.
thanks for this info.
My question is why is this important to you? See the FAQ article at
well, most of these 81 users are handled on our local system, but with different domains and TLDs (mainly 80% .de and 20% .org/.net). therefore we don't see any benefit in chunking here, especially in case 50% of the chunks are unused (.com,.edu/.us/.ca).
to simplify our logging-analysis in case of problems it seems beeter for us to have one entry for delivery to list-server and one entry for delivery from there.
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.
I understand, why chunking may have benefits perhaps in most situations, so it's set as default, but it would be great, to have the possibility to disable this without patching code, which might get overwritten with an update.
omf.