Re: Why is it VERPing every message?
On Tue, Jun 23, 2026, at 8:48 PM, Mark Sapiro wrote:
I don't know what the issue is, but even if you have personalization off, try setting
verp_personalized_deliveries: noin case there's some issue there.
Ok, that's weird. mailman conf -s mta said it was already set to no, but I added it to /etc/mailman3/mailman.cfg and now it's sending in big chunks. Which now RoadRunner is rejecting because of too many recipients in one message instead of too many simultaneous connections. Can't win with these idiots, can I?
-- Paul Tomblin
On 6/24/26 13:01, Paul Tomblin via Mailman-users wrote:
On Tue, Jun 23, 2026, at 8:48 PM, Mark Sapiro wrote:
I don't know what the issue is, but even if you have personalization off, try setting
verp_personalized_deliveries: noin case there's some issue there.Ok, that's weird.
mailman conf -s mtasaid it was already set to no, but I added it to /etc/mailman3/mailman.cfg and now it's sending in big chunks. Which now RoadRunner is rejecting because of too many recipients in one message instead of too many simultaneous connections. Can't win with these idiots, can I?
Did you set max_recipients in the mta section of mailman.cfg. That controls the maximum number of recipients of a message. The default is 10. Is that the number of recipients you're seeing in the rejected messages.
On the other hand, your MTA might be combining recipients from two or more messages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, Jun 25, 2026, at 12:00 AM, Mark Sapiro wrote:
On 6/24/26 13:01, Paul Tomblin via Mailman-users wrote:
Did you set max_recipients in the mta section of mailman.cfg. That controls the maximum number of recipients of a message. The default is 10. Is that the number of recipients you're seeing in the rejected messages.
Right now it appears to be obeying the destination_recipient_limit (5) in my postfix configuration, but it's not obeying the destination_concurrency_limit (1), and hitting their servers with a bunch of connections at the same time. My research into postfix configuration continues.
I wonder if I should set max_recipients to 0 in Mailman, and let Postfix decide how many recipients, if things would be a bit happier?
-- Paul Tomblin
Paul Tomblin via Mailman-users writes:
Right now it appears to be obeying the destination_recipient_limit (5) in my postfix configuration, but it's not obeying the destination_concurrency_limit (1),
Is that a typo? In <https://www.postfix.org/postconf.5.html> I didn't finad a mention of 'destination_concurrency_limit', rather a family of "default_destination_concurrency_limit" and "$TRANSPORT_destination_concurrency_limit" variables for $TRANSPORT = "smtp", "lmtp", "local", etc. (Similarly for "*_destination_recipient_limit".)
Also note that "*_destination_recipient_limit = 1" changes the meaning of the corresponding "*_destination_concurrency_limit" from "per domain" to "per recipient". From what you write above this isn't an issue in your configuration, but remember that "1" is special here.
and hitting their servers with a bunch of connections at the same time. My research into postfix configuration continues.
I wonder if I should set max_recipients to 0 in Mailman, and let Postfix decide how many recipients, if things would be a bit happier?
This is more likely to give you full control over a mail flow than having Mailman decide. In general it's better to configure limits as close to the agents you *don't* control as possible so downstream agents in your system don't mess with it. For example, if you have a set of messages to a site that all have temporarily failed, Postfix will likely batch them up for retry. Mailman can't do anything about that. Also, probably more important from your point of view, is that Postfix can deal with draconian limitations at one recipient domain and be more performant at sane domains. Mailman can't.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
On Thu, Jun 25, 2026, at 8:22 AM, Stephen J. Turnbull wrote:
Paul Tomblin via Mailman-users writes:
Right now it appears to be obeying the destination_recipient_limit (5) in my postfix configuration, but it's not obeying the destination_concurrency_limit (1),
Is that a typo? In <https://www.postfix.org/postconf.5.html> I didn't finad a mention of 'destination_concurrency_limit', rather a family of "default_destination_concurrency_limit" and "$TRANSPORT_destination_concurrency_limit" variables for $TRANSPORT = "smtp", "lmtp", "local", etc. (Similarly for "*_destination_recipient_limit".)
I was over simplifying there - I made a new transport called “slow_smtp” and made rr.com use it through /etc/postfix/transport, then set slow_smtp_destination_concurrency_limit. Same with the slow_smtp_recipient_limit.
-- Paul Tomblin
participants (3)
-
Mark Sapiro -
Paul Tomblin -
Stephen J. Turnbull