Journal error

I am getting the below error in the journal but unable to find the root cause of this error, please help me out below is the error logs.
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: caused by: invalid header: 0: at line 2, in Eof:
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: consultantcorner@hdfclife.com
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: ^______________________________
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: 2024-03-23T18:02:06.723933Z ERROR localset-4 run{socket=PollEvented { io: Some(TcpStream { addr: 10.4.1.101:…ack error
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: stack traceback:
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: [C]: in method ‘from_header’
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: [string “/opt/kumomta/etc/policy/init.lua”]:197: in function <[string “/opt/kumomta/etc/policy/init.lua”]:151>
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: caused by: invalid header: 0: at line 2, in Eof:
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: consultantcorner@hdfclife.com
Mar 23 23:32:06 ip-10-4-1-101.ap-south-1.compute.internal kumod[3111]: ^______________________________

Hey there @youthful-zorse, while we would like to respond to every question raised here, the frequency and nature of your questions are far beyond what we at Kumo Corp can support without financial support from your organization.

You may continue to ask questions in the hope that someone from the broader community will help, but you should expect that Kumo Corp will not spend any time beyond a cursory glance to see if your questions are well-qualified and can be easily dealt with.

That error message says your mail from is malformed

Sorry Tom I didn’t understand your point, if possible can you please explain it with an example

Maybe take a look at like 151 of your init.lua?

on that particular line I am fetching from domain, for dkim sign

Ok. The line above it refers to 197 as well. These error messages are usually pretty straight forward. My guess is that you have a malformed mail from header.

Full information would be helpful. What is the exactly message you are injecting and how? Can you show the trace of the SMTP conversation? What is the current Init.lua? Do you have any debugging in place to shw the fields as they are being processed?

If I were debugging this, I would be adding that debugging and I suspect I would find a malformed header field. The journal messages are usually accurate, though you may need to dig for the exact cause.