Connection_limit for specific IP

KumoMTA Traffic Shaping
1

Is there any way to configure a connection_limit for a specific Egress Source in the shaping.toml? I search something like:

["*".sources."IP-1"]
connection_limit = 3
3

I feel that this part does not support wildcards.

4

Maybe should use lua code.

5

What is your use case for wanting to set a global outbound connection limit for an IP?

6

I need to adjust some settings of specific IPs. Previously I used PowerMTA with these settings:

<domain *>
    max-smtp-out                       5
    max-msg-per-connection             70
</domain>

If there is any way to edit the settings for specific IPs (or pools/tenants if possible), it would help a lot.

7

A use case is a “Why” not a “What”, you have not provided a use case.

8

We have a customer who sends over a dedicated IP and requires specific settings (such as connection limits). Unfortunately, we don’t know exactly why these values were originally configured this way in PowerMTA — the colleague who set them up is no longer with the company, and there’s no documentation about it. Since we’re currently migrating from PowerMTA to KumoMTA, we’re trying to replicate the existing configuration as closely as possible.

9

This sounds more like an opportunity to bring an undocumented outlier into conformance. We have global settings that affect how all IPs interact with their destinations, including default rules. We have setting to allow for shaping how a given IP talks to a given destination (because that specific IP has reputation with that specific destination), but we have no use cases for why a specific IP should behave differently when talking to all destinations.

I’m not even sure this is something where we’d make our usual suggestion of sponsoring a desired feature, because again we’d need both a sponsor and a use case.