available in current dev builds
I’ll switch over to dev branch (we prefer stable release) and report back the results. Any other handlers affected or get_queue_config was the odd one that slipped by the radar?
depending on the version you are running, it may also call get_egress_path_config during that phase of queue insertion
Running latest stable kumod 2024.09.02-c5476b89. Safe there since running shaper configs from docs
local shaper = shaping:setup_with_automation {
publish = { '<%= @traffic_shaper_url %>' },
subscribe = { '<%= @traffic_shaper_url %>' },
extra_files = {
'/opt/kumomta/etc/policy/shaping_base.toml',
'/opt/kumomta/share/community/shaping.toml',
'/opt/kumomta/etc/policy/shaping_tweaks.toml',
},
}
kumo.on('get_egress_path_config', shaper.get_egress_path_config)
Pardon the chef erb templates
Network errors happen…
Would one cause the same problem?
as I said, no one has seen this in production
network errors in tsa don’t bubble up through here
Just makig sure we don’t double-deliver
I got like 80 copies of by the sheer fact of MSA trying to submit the mail again ![]()
Testin env ofc