Showing some error in log

get-help
1

{“type”:“Rejection”,“id”:“”,“sender”:“”,“recipient”:“”,“queue”:“”,“site”:“”,“size”:0,“response”:{“code”:501,“enhanced_code”:null,“content”:“Syntax error in command or arguments: → 1:1 | 1 | | ^— | = expected mail, rcpt, ehlo, helo, data, rset, quit, vrfy, expn, help, noop, starttls, or auth”,“command”:null},“peer_address”:{“name”:“”,“addr”:“45.0.0.0”},“timestamp”:1719900142,“created”:1719900142,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“received_from”:“45.0.0.0:32685”},“headers”:{},“delivery_protocol”:null,“reception_protocol”:null,“nodeid”:“4b7fdc75-b207-44b1-8523-6365384203c0”}

While checking kumomta log, showing some errors that is not understandable. Iam using Golang package to sent emails

2

Hey there @kindhearted-deer, 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.

3

{“type”:“Rejection”,“id”:“”,“sender”:“”,“recipient”:“”,“queue”:“”,“site”:“”,“size”:0,“response”:{“code”:501,“enhanced_code”:null,“content”:“Syntax error in command or arguments: → 1:1 | 1 | OPTIONS sip:nm SIP/2.0 | ^— | = expected mail, rcpt, ehlo, helo, data, rset, quit, vrfy, expn, help, noop, starttls, or auth”,“command”:null},“peer_address”:{“name”:“”,“addr”:“45.0.0.0”},“timestamp”:1719900182,“created”:1719900182,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“received_from”:“45.0.0.0:15405”},“headers”:{},“delivery_protocol”:null,“reception_protocol”:null,“nodeid”:“4b7fdc75-b207-44b1-8523-6365384203c0”}

{“type”:“Rejection”,“id”:“”,“sender”:“”,“recipient”:“”,“queue”:“”,“site”:“”,“size”:0,“response”:{“code”:501,“enhanced_code”:null,“content”:“Syntax error in command or arguments: → 1:1 | 1 | From: sip:nm@nm;tag=root | ^— | = expected mail, rcpt, ehlo, helo, data, rset, quit, vrfy, expn, help, noop, starttls, or auth”,“command”:null},“peer_address”:{“name”:“”,“addr”:“45.0.0.0”},“timestamp”:1719900182,“created”:1719900182,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“received_from”:“45.0.0.0:15405”},“headers”:{},“delivery_protocol”:null,“reception_protocol”:null,“nodeid”:“4b7fdc75-b207-44b1-8523-6365384203c0”}

4

Please check the content part in the reception error and you will find the error occurred.

5

there is no reception log. generating 2 rejection log.

6

{“type”:“Rejection”,“id”:“”,“sender”:“”,“recipient”:“”,“queue”:“”,“site”:“”,“size”:0,“response”:{“code”:535,“enhanced_code”:{“class”:5,“subject”:7,“detail”:8},“content”:“AUTH invalid”,“command”:null},“peer_address”:{“name”:“smtp.mailrcld.com”,“addr”:“10.0.0.0”},“timestamp”:1720082020,“created”:1720082020,“num_attempts”:0,“bounce_classification”:“AuthenticationFailed”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“received_from”:“10.0.0.0:55962”},“headers”:{},“delivery_protocol”:null,“reception_protocol”:null,“nodeid”:“cc30c0ba-63a1-41a9-b189-5282a4aae045”}

{“type”:“Rejection”,“id”:“”,“sender”:“”,“recipient”:“”,“queue”:“”,“site”:“”,“size”:0,“response”:{“code”:501,“enhanced_code”:null,“content”:“Syntax error in command or arguments: → 1:1 | 1 | * | ^— | = expected mail, rcpt, ehlo, helo, data, rset, quit, vrfy, expn, help, noop, starttls, or auth”,“command”:null},“peer_address”:{“name”:“smtp.mailrcld.com”,“addr”:“10.0.0.0”},“timestamp”:1720082020,“created”:1720082020,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“feedback_report”:null,“meta”:{“received_from”:“10.0.0.0:55962”},“headers”:{},“delivery_protocol”:null,“reception_protocol”:null,“nodeid”:“cc30c0ba-63a1-41a9-b189-5282a4aae045”}

7

Issue has been fixed.