TSA shaping file doesn't seem to update?

KumoMTA Traffic Shaping
22

Let me try sth else!

23 
[provider."xxxx"]  
match=[  
    {MXSuffix="xxx.com"},  
    {MXSuffix=".xxxx.com"}  
]  
connection_limit = 1  
max_deliveries_per_connection = 1  
max_message_rate = "1/m"

["default"]  
connection_limit = 1  
max_deliveries_per_connection = 1  
max_message_rate = "1/m"
24

Nope, nothing

25 
curl -s 'http://localhost:8008/get_config_v1/shaping.toml' | head
# Generated by tsa-daemon
# Number of entries: 0

However, it throttled the connections!

26

SCHEDULED QUEUE COUNT
1:@gmail.com 0
1:@xxxxxxxxxxxxxxx 49
webhook.log_hook 0

27

Apparently, there’s 49 emails in the scheduled queue atm

28

And it’s sending one per minute

29

Well it works. The ticket may be closed, but for some reason, the TSA generated shaping file does not have any data.

30

The live data available when you call the TSA node directly will be “immediate”. If there are no traffic shaping automations currently in effect, the file will be blank. In most cases, the data will be an hour or less old.

31

I am pretty sure thsi will not trigger anything:
regex = ""

32

as opposed to “will trigger on anything”

33

you might want regex = ".*"

34

but that will literally trigger on any report

35

Suspensions don’t generate shaping configuration changes; they generate suspensions! You can review suspensions that are active on a kumo mta node via kcli suspend-list. You can see the current set that TSA is maintaining by curling http://localhost:8008/get_suspension_v1/suspended.json

36

Is there a way to test the TSA daemon to maybe suspend all queues for testing?

37

Not sure what you mean. Do you actually want to suspend everything on purpose?

38

Yeah :slightly_smiling_face: Just to test it out

39

You can use kcli suspend —everything to force it manually

40

Or use the trigger command I posted above

41

thank you, ill have a look tn!!