I’m on phone so the screenshot is small, which resource is over-used?
One moment. I don’t think this is an issue with Kumo
Looks like one of the emails sent by our client was malformed and our connector kept hammering KumoMTA with that email again and again. Which obviously resulted in very high CPU usage.
Let me patch that up
My bad guys
Jan 13 23:37:00 mta3 mta-connector[11659]: 1 | RCPT TO:<�learmonte@XXXXXXXXXXXXXXXXX>
Jan 13 23:37:00 mta3 mta-connector[11659]: | ^—
Jan 13 23:37:00 mta3 mta-connector[11659]: |
Jan 13 23:37:00 mta3 mta-connector[11659]: = expected local_part or at_domain
Interesting situation
So one of the clients’ emails contained � for some reason
Kumo just rejects the email address
Pretty funny because Golang’s official mail validator thinks that it’s a valid email address
Replacement character � should be valid as per RFC 6532
But obviously not practical
I just tried it with Gmail.
Delivered-To: XXXXXXXXXXX+�@gmail.com
Worked fine
It looks like Gmail doesn’t mind it
I’m just gonna add a rule to reject any emails with this character
One thread per question pls.
Yep, no stress. It was related because it was causing my connector to keep sending the failed email again and again
But gotcha, thank you
