Possibly more a Postfix question than a mailman one one but...
I want to limit the number of simultanous connections for one domain that I send email to. According ot what i've managed to find on-line, I need to put in a transport map in Postfix for that. But Mailman appears to already be using the transport map for routing incoming mail:
transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname, $alias_maps, hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains
Can i append or pre-pend another transport file in the transport_maps listing and put in the entry for this domain that's been bouncing people off my list because of too many simultaneous connections?
-- Paul Tomblin
On 6/12/26 3:03 PM, Paul Tomblin via Mailman-users wrote:
Can i append or pre-pend another transport file in the transport_maps listing and put in the entry for this domain that's been bouncing people off my list because of too many simultaneous connections?
I don't know what the transport for this domain would be, but the transport_maps setting can contain any number of lookup tables. See <https://www.postfix.org/postconf.5.html#transport_maps>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, Jun 12, 2026, at 6:46 PM, Mark Sapiro wrote:
On 6/12/26 3:03 PM, Paul Tomblin via Mailman-users wrote:
Can i append or pre-pend another transport file in the transport_maps listing and put in the entry for this domain that's been bouncing people off my list because of too many simultaneous connections?
I don't know what the transport for this domain would be, but the transport_maps setting can contain any number of lookup tables. See <https://www.postfix.org/postconf.5.html#transport_maps>.
It appears you set up a transport with a lower concurrency limit in master.cf like so: slow_smtp unix - - n - - smtp -o slow_smtp_destination_concurrency_limit=5
Then you put an entry in your transport map like so: example.com slow_smtp:
I believe I had something similar on my previous server, but I discarded it because I wasn't sure how well it would play with this lmtp stuff that Mailman was putting in. But remember how I was getting dozens of people bounced off one of my lists all at once, and most of them were at a particular domain? Yeah, this is the underlying cause. Our biggest local ISP doesn't like it when I've got 3 emails going out, and 30+ people at that domain on all of them.
-- Paul Tomblin
On 6/12/26 3:54 PM, Paul Tomblin via Mailman-users wrote:
Then you put an entry in your transport map like so: example.com slow_smtp:
so you could put that line in a file like /path/to/name and process it with
postmap hash:/path/to/name
and then change your transport_maps setting from
transport_maps =
hash:/opt/mailman/mm/var/data/postfix_lmtp
to
transport_maps =
hash:/opt/mailman/mm/var/data/postfix_lmtp hash:/path/to/name
-- 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 -
Paul Tomblin