setting up defaults for a tenant in shaping.toml

get-help
1

Just a quick question… If I want to setup default settings for a tenant in the shaping.toml helper file would it look like this: (where warmup_tenant is the tenant name I defined in the smtp_server_message_received pased on the received_via meta data)

[ 'default'.'warmup_tenant']
connection_limit = 2
max_connection_rate = "10/min"
max_deliveries_per_connection = 10
max_message_rate = "5/s"

Since I found some documantation on shaping for a tenant which looked like the example below. Ifigured the syntax for the default tenant behaviour be like the above.

[queue.'gmail.com'.'mytenant_alerts']
max_age = '12 hours'
retry_interval = '5 mins'
3

Default tenant syntax is:

default_tenant = "default-tenant"

[tenant.'default-tenant']
egress_pool = 'pool-1'
4

hmm so also in the shaping.toml I should address it like that.. (just to be sure)… will do some more testing on my dev server, but can’t access that atm :slightly_smiling_face:

5

In the queue.toml you have the egress_pool configuration with that … thanks. could not make my mind up on this.

6

I tried using:
[tenant.‘warmup’]
connection_limit = 1
max_connection_rate = “10/min”
max_deliveries_per_connection = 10
max_message_rate = “5/s”

And a kumod --validate will say this:
Entry for domain ‘tenant’ consists of a single DNS label. Domain names in TOML sections need to be quoted like '[“tenant.com”]` otherwise the ‘.’ will create a nested table rather than being added to the domain name.

7

so I am not using the right syntax in the shaping.toml

8

tenants belong in the queue.toml and the queue helper, not in the shaping.toml/shaping helper

9

shaping is carried out on a source → site basis, and the tenant doesn’t apply there

10

so what I want is set default max_messages_rate for a tenant. I will check again in the docs if that can be done. I was a bit confused by the default settings in the shaping.toml, so I assumed you could do that also for a tenant.

11

shaping is carried out from the perspective of the receiving site; they see only your source ip, they don’t know about your tenant

12

you can set overall_max_message rate in the queue.toml for a tenant. That throttles the rate at which messages move from any/all scheduled queues associated with that tenant and into the ready queue for delivery

13

I don’t see this option mentioned in the docs… but usage is like this in your queue.toml for the queue helper:

[tenant.'mytenant']
egress_pool = 'tpool'
overall_max_message_rate = "100/s"
14

thanks I will give that a try