Trying to follow instructions from my injector (I asked them to integrate with KumoMTA) but I’m getting this error. I’ll paste my init.lua in a moment.
Hey there @poised-goat, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
message.txt (10.9 KB)
I’m wondering if it’s an error in the order I put things into my config, I think I saw another post about that
ah, yes I see Wez mentioned it here:
https://discord.com/channels/1072980126737907824/1181266923451854848/1181274785007816734
so, if I’m understanding myself correctly (big if):
- I do have my kumo.configure_log_hook in the init, WELL before the rest of it (starting at the
kumo.on('should_enqueue_log_record'bit
I’m wondering if they instructions my injector wrote are for a newer version of Kumo than what I have…I should go check the release notes
There are 2 parts to the webhook process. 1) Defining the hook and 2) triggering it
Theses should both be outside of the init section
I thing the sample config shows a webhook definition.
You can also use the log hook helper
I’d recommend using the log hook helper; it’s much easier to use and more self contained
the key bits are:
local log_hooks = require 'policy-extras.log_hooks'
-- Send a JSON webhook to a local network host.
-- See https://docs.kumomta.com/userguide/operation/webhooks/
log_hooks:new_json {
name = 'webhook',
url = 'http://10.0.0.1:4242/log',
log_parameters = {
headers = { 'Subject', 'X-Customer-ID' },
},
}
cool, I’ll try switching to the loghook helper and see if that works
that worked great, not sure why we were trying it the other way 
Awesome. 
I let the platform know to update their documentation. fingers crossed they get some additional clients who see Kumo as an option now and will try it out!
Wait, our documentation? I thought I updated that.
no no
THEIR documentation