Well that was thought too.. I was ‘strace’-ing the OPS and it was checking memory use and some memory.max stuff
I might try to build a Debian 12 souce binary at some point… but when initial testing it just worked fine.
Anyway… thanks for the quick response
as I am working on the shaping.toml how can i validate if the tsa daemon is actually using it..
curl -s ‘http://localhost:8008/get_config_v1/shaping.toml’ is only showing me the default settings from the extra-policy
taps the first reply where it shows that to get help you show your configs
That will show you what is currently in the TSA resource and it changes depending on feedback. If you tail that while sending and the rates change, you will see the values change. You can technically force it if you want to test it but adding a rule you know will trigger.
I think I see what you mean though. You can see what is in there now and you can test if TSA is running, but you can’t see if the two are “really” connected. It might warrant an enhancement request. I get that visibility and trust are important.
One other thing I see needs some documentation is the shaping validation tool. This is available in the code, but is not really documented. I can fix that.
/opt/kumomta/sbin/validate-shaping
^^ That will do a syntax validation of your shaping file, but will not tell you if TSA is working.
Hmmm it is good that you point that out… I was going to continue the shaper config… and restarting kumo to see if it parses or not 
but for now the kumomta-dev is still working even with customer mail going through.
Fantastic!
I did build a Debian 12 binary of the old version… I might test it to see if that breaks again
but I remember having it on a virtualbox machine too… so I will see what I can find..
I probably will need to read more docs.. but how can I deliver updated shaping.toml configs to the project?
As in sharing shaping information with the community?
or you can drop a note here in the get-help area asking for it to be added and we will take care of it.
If you mean just adding your own custom shaping configs to your own project, then…
You can add your own custom overrides like that ^^
well the latter is what I am doing now to test stuff But I think I would like to get all the yahoo.com TS02 and TS04 feedback errors codes in there… so Kumo will deliver better. Oh and set sensible defaults off course