Haraka Mailserver Logs show loopback_is_rejected errors
-
Hi there,
today I discovered, that I get (maybe every 30 Minutes?) the following errors:
2024-12-29T04:11:07Z TypeError: Cannot read properties of undefined (reading 'loopback_is_rejected') 2024-12-29T04:11:07Z at exports.checkZoneNegative (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:347:22) 2024-12-29T04:11:07Z at exports.check_zone (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:372:20) 2024-12-29T04:11:07Z at async Promise.all (index 1) 2024-12-29T04:11:07Z at async exports.check_zones (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:393:5)
Is this something we should be concerned?
Best,
Mike -
I don't VPN and the error occures not related to sending emails
-
No VPN for me either and I saw this same
loopback_is_rejected
error in my logs which I pasted for a possibly related issue here: https://forum.cloudron.io/topic/12974/hetzner-ptr-record-invalid/12?_=1735543281810By any chance are you on 8.2.0? or 8.2.1?
-
-
@nebulon thx, I tried, no errors during redo, but the result is the same. DKIM is still missing for outgoing emails. I will continue to monitor if the looopback error still appears.
The loopback error still exist:
Dec 30 13:11:07 TypeError: Cannot read properties of undefined (reading 'loopback_is_rejected') Dec 30 13:11:07 at exports.checkZoneNegative (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:347:22) Dec 30 13:11:07 at exports.check_zone (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:372:20) Dec 30 13:11:07 at async Promise.all (index 1) Dec 30 13:11:07 at async exports.check_zones (/app/code/haraka/node_modules/haraka-plugin-dns-list/index.js:393:5)
-
@nebulon I can confirm sync DNS doesn’t do anything to fix the issue. The issue isn’t DNS, I think it’s in the Haraka SMTP side. Please refer to the other thread too where there’s some more details. I think these two threads are effectively the same issue around DKIM not working.
-
The error here is unrelated to the DKIM issue. This seems to come from the dnsbl plugin. I am submitting a PR upstream to fix it.
-