Yes, I did this all along, but it didn’t work.
kumo_init.lua (3.27 KB)
I can’t send logs and smtp traces to them now.
But I can do it in a little while.
Your smtp_server_message_received does not have the required code from the link in the documentation I provided.
Also move your dkim signing to the last part of that event handler.
Is that what you mean?
kumo.on('smtp_server_message_received', function(msg)
if msg:recipient().domain == 'bounce.examplecorp.com' then
-- Re-route the message to the intended destination
msg:set_meta('routing_domain', '[192.168.1.100]')
-- In earlier versions of KumoMTA, you need to set the queue
-- this way instead
-- msg:set_meta('queue', '[192.168.1.100]')
end
end)
It is.
And of course you can omit the bottom commented part.
The routing domain is set to either the IP or the hostname of the machine that needs to receive the DSN message. You have to set routing because if we relay it to the MX for the bounce domain it’s right back to KumoMTA since KumoMTA is the MX host.
Yes, I tried this part during the day, now it is indeed not included in init.lua.
It is also clear that it has to be added because of the mx.
But despite all this, the DSN has not arrived.
I would like some time to set everything up again and try it all the way through.
I’ll be in touch soon.
Thank you very much for your help so far.
I went through it again and set everything up.
But no DSN emails have arrived in the bounce@probaterem.hu account, and I don’t see anything on the smtp server that manages it.
I’ll send you the logs.
init.lua (3.38 KB)
log.txt (1.99 KB)
smtp_trace.txt (3.64 KB)
swaks.txt (1.1 KB)
First glance: ‘[mail.webdream.hu]’
Remove the , those are for using IP literals where a hostname is expected, and you’re passing an hostname.
Ok, removed it.
Now I only get one log, Reception.
No bounce log.
waiting for more files
/srv/kumomta/log/20240919-142809_recv
{"type":"Reception","id":"64e48f2e769311efa8b1bc2411885e85","sender":"bounce+info=iuno.hu@probaterem.hu","recipient":"asdasdasdbranko@indamail.hu","queue":"Site-A@indamail.hu","site":"","size":1164,"response":{"code":250,"enhanced_code":null,"content":"","command":null},"peer_address":{"name":"prometheus","addr":"10.252.1.187"},"timestamp":1726756089,"created":1726756089,"num_attempts":0,"bounce_classification":"Uncategorized","egress_pool":null,"egress_source":null,"source_address":null,"feedback_report":null,"meta":{},"headers":{"Subject":"test Thu, 19 Sep 2024 16:28:09 +0200","From":"bounce+info=iuno.hu@probaterem.hu","To":"asdasdasdbranko@indamail.hu"},"delivery_protocol":null,"reception_protocol":"ESMTP","nodeid":"160e1749-8eb7-4d0d-b589-e107a8eb556e"}
waiting for more files
So when you got the routing setup you did not get a bounce record? Did you get a delivery to the next node?
That’s right, I didn’t get anything.
I don’t even see a connection attempt on the smtp it should have arrived on.
- Nothing is down on the firewall
- Nothing down in fail2ban
- telnet to the other smtp works.
Dear Mike!
I didn’t change yesterday’s config, I just run kumomta in debug mode directly from the console.
Two separate incidents happened with the same swak command:
swaks --to asdasdasdbranko@indamail.hu --from bounce+info=iuno.hu@probaterem.hu --server smtp-iunox.webdream.lan --port 25
- In the first case, after the recv log, I got a TransienFailure log, attached separately. Here it describes a TLS problem when connecting to mail.webdream.hu ( 10.1.1.7 ).
- In the second case, after the recv, I got a Bounce type log.
I attach these as separate files.
I am puzzled by the TLS problem, I will investigate further.